Network Connections
The following figure is a diagram that shows all the connections needed for Code Pipeline to integrate with
BMC AMI Common Enterprise Services
(CES
) andWorkbench for Eclipse
, depending on the versions you are running for each.Network connections for Code Pipeline integration
Configuration example diagrams
The following figures provide a template to follow for identifying all the parameters that must be updated and the ports that must be kept in sync to support
Code Pipeline
on the mainframe,
Workbench for Eclipse
, HCI/CMSC, and
CES
.
Parameters and ports
The following table lists the related parameters and ports.
Single LPAR parameters and ports
CM Parameters | CI Parameters | CT Parameters | CMSC Ports | HCI Ports |
|---|---|---|---|---|
SERVERID | SERVERID | SERVERID | CES_HOST | HCI_HOST |
WZCMNAME | WZCMNAME | WZCMNAME | CES_PORT | HCI_PORT |
WZCINAME | WZCINAME | WZCTNAME | ISPW_HOST | |
WZCTNAME | XSYSPROT | XSYSPROT | ISPW_PORT | |
XSYSPROT | WZCMADDR | WZCMADDR | ||
WZCMADDR | WZCMPORT | WZCMPORT | ||
WZCMPORT | TCPUSERID | WZCTADDR | ||
WZCMXPRT | XMEMID | TCPUSERID | ||
TCPUSERID | ||||
*WEBAPI=Y | ||||
*CUSTOMDIALOGS | ||||
*CONFIGNAMES |
Configuration considerations
- The minimum releases for each product are Code Pipeline 18.02,
Workbench for Eclipse
18.03,CES
18.03, and ECC
17.02 (for HCI and CMSC).- All ports are listening ports.
- For the parameter CUSTOM_DIALOGS, specify Y (Yes) if you want to enable the use of custom generate dialogs. The default is N (No).
- For the parameter CONFIG_NAMES, specify Y (Yes) to enable loading a list of valid runtime configuration names for this CM. See Define CM Specific Parameters in Milestone-8-Define-Started-Tasks for more information. The default is N (No).
- The ISPW_PORT must match the WZCMXPRT.
- Host Connection settings are used to specify port connection to the HCI. There must be at least one HCI port configured per LPAR.
- You must specify the HCI_PORT as a
Workbench for Eclipse
user or inCES
. This should be entered under Host Connections for the Port field.
Single LPAR
The following figure illustrates a single LPAR.
Simple Single LPAR Code Pipeline configuration
The following figure illustrates a simple single Code Pipeline LPAR configuration.
Workbench for Eclipse for Code Pipeline configuration
The following figure illustrates
Workbench for Eclipse
for Code Pipeline Configuration.
CES
REST API/Webhooks for Code Pipeline configuration
The diagram in the following figure uses the same CM and HCI as those shown in the
Workbench for Eclipse
for Code Pipeline Configuration diagram.CES
REST API/Webhooks for
Code Pipeline
configuration
Adding a CT and/or CI for a remote LPAR
On the M.SV screen, add entry:
- Server Name - ISPWCT
- System Type - MVS
- Server Type - CT
- Address - IP address of Code Pipeline CT
- Socket - Port for file transfers from other CT/RMT SRVR/Topaz 18.2
- CSS Socket - Port for Topaz 18.2+
- Deploy - Y/N
- Description - Default MVS CT SERVER
Adding a CT and/or CI for a remote LPAR
