Welcome to the System z Management Blog, where you can read the perspectives from System z experts. This Blog provides insights into the System z solution, as well as technical details about specific IBM products.
The developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
Common Data Provider for z Systems Now Provides a Liberty Based Configuration Tool
Common Data Provider for z Systems now includes a Liberty Based Configuration Tool as of 3/4/19. This Configuration Tool installs into WebSphere Application Server Liberty for z/OS, which Common Data Provider now includes as a DVD image. It is introduced in Common Data Provider's UA98625 PTF. The z/OSMF based configuration tool is still supported and is recommended for customers who prefer to use z/OSMF to manage their z/OS environment. For customers who don't have z/OSMF implemented, this Liberty Based Configuration Tool provides another option. Because the Liberty based Configuration Tool is essentially the same as the z/OSMF based Configuration Tool, any policy files created can be interchanged between the two. This Liberty based Configuration Tool can be set up in under 2 hours.
Obtaining WebSphere Application Server Liberty for z/OS Packaged with Common Data Provider
For new and existing Common Data Provider customers, you must order Common Data Provider from shopZ to obtain its copy of WebSphere Application Server Liberty for z/OS.
The Liberty server component will be under the "CD/DVD Images and Other Material" section of your order.
If you placed an electronic order, click check box for "IBM WebSphere Application Server Liberty for z/OS in DVD Format", and click the download button.
Navigate to the folder created by the download director, and note there is an ISO file that contains all of the WebSphere Application Server Liberty for z/OS files.
The following files are included in the ISO image:
The README.txt file should be used to set up the WebSphere Application Server Liberty for z/OS app on your z/OS system.
Setting Up the Liberty Based Configuration Tool
The following steps demonstrate the streamlined workflow of quickly setting up the Liberty Based Configuration Tool in your environment:
Install WebSphere Application Server Liberty for z/OS per instructions included on its DVD.
Post SMP/E installation of UA98625
Run the defracf.cmd script to define RACF resources needed by this Liberty Based Configuration Tool.
Go to /usr/lpp/IBM/cdpz/v1r1m0/UI/LIB and execute command /usr/lpp/IBM/cdpz/v1r1m0/UI/LIB/defracf.cmd
Defaults can be taken for all prompts by this script except authorized_user (the user authorized to access the Configuration Tool). The user ID entered for this prompt must be an existing SAF user.
Run the savingpolicy.sh script to create a directory structure needed to support the configuration tool with added support for WebSphere Application Server Liberty for z/OS.
Run the command sh /usr/lpp/IBM/cdpz/v1r1m0/UI/LIB/savingpolicy.sh.
At the first prompt choose option '2' to create a configuration tool environment in Liberty server.
Defaults can be taken for the remaining prompts. Ensure that path to Java in your environment is correct when prompted for Java location.
Copy the started tasks HBOCFGT and HBOCFGA needed by the configuration tool Liberty server and angel server from hlq.V1R1M0.SHBOSAMP to your PROCLIB dataset.
In HBOCFGA update the path to the Liberty file system created in the first installation step above (WLPDIR='/u/liberty/wlp'), where /u/liberty represents the mount point you used for the newly defined Liberty filesystem.
In HBOCFGT update the path to the Liberty file system created in the first installation step above (SET INSTDIR='/u/liberty/wlp'), where /u/liberty represents the mount point you used for the newly defined Liberty filesystem. Also update the path to the Configuration Tool directory if you chose a different directory path when savingpolicy.sh script was run. (SET USERDIR='/var/local/CDPServer') statement represents the default Configuration Tool path that savingpolicy.sh creates.
Start the angel server by running the z/OS system console command: S HBOCFGA
In HBOCFGA's JOBLOG you will see "CWWKB0069I INITIALIZATION IS COMPLETE FOR THE HBOCFGA ANGEL..." message when this procedure starts successfully.
Start the Configuration Tool server by running the console command: S HBOCFGT
In HBOCFGT's JOBLOG you will see "CWWKF0011I: The server cdp_ui_server is ready to run a smarter planet." message when this procedure starts successfully.
You are now ready to sign onto Common Data Provider's Liberty based Configuration Tool user interface and create/manage policies. The URL to access the Configuration Tool in your environment is echoed in the HBOCFGT's JOBLOG.
Interchanging Common Data Provider Policy Files Between z/OSMF Based Configuration Tool and the Liberty Based Configuration Tool
By default the Liberty Based Configuration Tool creates and saves files to a directory named /var/local/CDPServer/cdpConfig and the z/OSMF based Configuration Tool creates and saves files to /etc/cdpConfig.
You can use the cp command to copy policy files between the directories used by either Configuration Tool.
Once you restart the Configuration Tool, you will see the newly copied policy(s).
authorized_user user ID is sometimes not found when defracf.cmd script does a lookup for an existing user ID supplied by the customer. This has been seen on systems where zSecure command verifier modifies the standard output of RACF's LISTUSER command. In this instance defracf.cmd will not find an existing user ID it was told to look up.
Edit /var/cdp-uiconfig/cdpui.properties file.
Find authorized_user and erase the user ID to the right of the equal sign.
Rerun the defracf.cmd script and specify GO at the last prompt to cause the RACF commands to be executed.
Issue a manual "CONNECT USER GROUP(GROUP)", where USER is the user ID that the defracf.cmd script couldn't find and GROUP is the RACF group assigned to the authorized_group. This will allow the user specified on the CONNECT command to sign onto the Configuration Tool.