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.
Classify the services with WLM to give them the right priority
You can configure an API or service, for example https://10.1.3.10:9443/stockmanager/stock/items/999999, so it gets an appropriate service class in WLM, for example high priority.
You can use RMF to report on service classes to see the response time profile, and if the service class is meeting its performance goals.
See here for a good article.
This page gives the example
<wlmClassification> <httpClassification transactionClass="CLASS001" host="127.0.0.1" port="9080" method="GET" resource="/testResource" /> </wlmClassification>
You can classify the traffic depending on the IP address and port of the server, as well as the resource name.