The instructions I have seen for installing products based on Liberty that seem to be written as if there would only be one server; one server on the LPAR, and one server in the whole SYSPLEX. In reality you are likely to have the “same” server running on multiple LPARS sharing configuration to provide availability, and have more than one server running on an LPAR, for example MQWEB, WAS, z/OSMF, and z/OS connect. The series of blog post below are to help you implement multiple servers, across a sysplex.
Some of the areas not adequately addressed by the IBM product documentation include
- Sharing of definitions
- Sharing of keystore and trust stores
- Providing isolation, to prevent someone who has access to MQWEB from accessing Z/OS Connect.
- How many Angel tasks do I need – can one be shared?
- Some areas such as TLS can be hard to get working.
I’ll cover the instructions to install z/OS Connect, but the instructions are similar for other products. The steps are to create the minimum server configuration and gradually add more function to it.
The steps below guide you through
- planning to help you decide what you need to create, and what options you have to choose
- initial customisation and creating a server, creating defaults and creating function specific configuration files, for example a file for SAF
- starting the server
- enable logon security and add SAF definitions
- add keystores for TLS, and client authentication
- adding an API and service application
- protecting the API and service applications
- collecting monitoring data including SMF
- use the MQ sample
- using WLM to classify a service
With each step there are instructions on how to check the work has been successful.
I wrote the blog post How many servers do I need? Every one know this – or no one knows this. when I was first thinking about planning my servers.