About this blog
Thanks for choosing this blog to help you get sorted with IBM Db2 with BLU Acceleration Pattern for virtual systems, where you get to know about how to use or apply the Bring your own license (BYOL) option during the deployment of IBM Db2 with BLU Acceleration Pattern.
This blog provides you a great way to establish a connection between the user and the IBM Cloud Pak System appliance.
Read on. We hope that you find this blog helpful.
Introduction
IBM® Db2® with BLU Acceleration® Pattern is a plug-in that you can use to deploy database patterns and administer database instances on the virtual machines in the system. The plug-in contains default database patterns that you can immediately deploy, or you can create customized database patterns if you want to customize the configuration settings. Using database patterns can help you to eliminate the redundancies and issues that can result from manually creating database instances repeatedly.
Deploying database patterns
You can deploy a Db2® database by using one of the default database patterns that are provided on the system, depending on the workload type and features that your environment requires.
Deploying databases by using default patterns
You can deploy a Db2® database by using one of the default database patterns that are provided on the system, depending on the workload type and features that your environment requires. For more information, IBM Documentation has steps to deploy the default pattern.
Deploying custom databases by using the pattern builder
You can use the pattern builder to create and customize database patterns that are based on your specific requirements. For more information, IBM Documentation has steps to create customize a database pattern.
From the IBM Cloud Pak System user interface menu, go to Patterns > Virtual System Patterns. Select the desired pattern. Click the Open icon to open the pattern in the IBM Pattern Builder editor window, where you can customize the pattern.
Figure 1
Db2 license
The Db2 license is required when you deploy any of the Db2 pattern. If you use the IBM Cloud Pak Software System Suite offering, the Db2 license is already packaged. Therefore, there is no need to bring your own license (BYOL). If you use IBM Cloud Pak System or IBM Cloud Pak for System Software offerings, then you must bring your own license (BYOL) and apply it during deployment.
Db2 license during new deployment
Db2 license file in zip format parameter
The Db2 license must be in .zip format only. If it is an HADR pattern, then provide the license file for both primary and standby nodes. The name of the license archive file can be any name.
Figure 2
DB2 OEM License File Name parameter
If the zip file contains a Db2 OEM license (High-capacity license) as well, in addition to a Standard License with OEM High capacity License, then provide the Db2 OEM license file name in this field.
The default name of the Db2 OEM license (High Capacity license) is db2hc.lic. If you changed the name of the license file for any reason, then provide the new name in this field. (We suggest to keep the original name). For a single license file, you can ignore this field.
Available fixpacks parameter (Fix pack update during deployment)
You can also apply any new minor or special fix pack if it is released after the Cloud Pak System release. Download the new fix pack, rename to the Cloud Pak System required format and upload into Cloud Pak System by traversing to Pattern development -> DB2 Fix Packs.
For example, Db2 11.5.9 special build38015 is renamed in the following format as shown in the following figure: ()
Figure 3
After the fix pack is uploaded, it will appear under the Available Fix Packs dropdown list. For an HADR deployment, select the fix pack for both primary and standby nodes. For other patterns, select the fix pack for a single node.
Figure 4
Virtual System Instance pattern type upgrade scenario
Cloud Pak System and Cloud Pak System Software offerings
To update the existing Db2 V11.5 instances to a later version of Db2 pattern type, upload the compressed license file with the file name as db2license.zip to the storehouse. You can use the phuploader utility to upload the license file. The file must be stored under the admin/files/db2server/licenses/ folder in the storehouse. The phuploader utility is available on (Db2_License_phuploader_v1.0) IBM Fix Central.
Follow the readme file in the phuploader utility to upload the db2license.zip to the storehouse. If the license files contain the Db2 OEM license file as well, do not rename the OEM license file (i.e., keep the original file name as db2hc.lic). The db2license.zip file must maintain the file structure as follows and must not contain any extra files or folders. Ensure that you verify it before uploading to the storehouse:
- db2license.zip > db2adv_vpc.lic
- db2license.zip > db2std_o.lic, db2hc.lic
Note: The name of the license zip file must be db2license.zip.
Cloud Pak System Software Suite offerings
It is not required to upload the license in the storehouse for the pattern type update scenario, because the license file is already included.
Existing deployments Db2 fix pack update using post Manage Operations
If you want to update the Db2 with any minor fix packs or with any special builds for existing deployments, use the Manage Operations page of the Virtual System instance page. For more information, see the IBM Documentation for more steps on the page.
With this procedure, you are now successfully ready to use the IBM Db2 with BLU Acceleration Pattern for virtual systems and with the Bring your own license (BYOL).
We hope that you found this article helpful. For more information, feel free to reach out to the IBM Support team in this context.
I would like to thank Sudhir Pimpalkar and Anilkumar Hegde for their collaboration in writing this article.