Portus Version 2018-08-24
 

z/OS Server installation


Using the Deployment Wizard to install on a z/OS host
z/OS Server installation
      

Using the Deployment Wizard to install on a z/OS host

Note: If the version you are installing is not Portus v4.3.1, then your installation may display a version number different from the screenshots below. There is no functional installation difference between versions, so this can be safely ignored.

In preparation of running the Portus server on z/OS the installation datasets have to be deployed to the z/OS host. The deployment wizard on your Portus Control Centre on Windows or Linux can be used to deploy the required files to z/OS.

z/OS Server installation

Dataset Creation

Note: This step can be ignored if you chose the Create Datasets option in the Deployment Wizard. If so, continue to here

The Portus Installation on z/OS uses 4 datasets, which must be created in advance. The datasets can be any name you wish, so long as they each use the same high-level qualifier. This allows the user to specify one dataset name prefix in the Java wizard, and the installation is based upon this qualifier.

The 4 datasets to create are RECV, JCL, CONF, and ZIP.

For example, if the high-level qualifier is USER.INST001, then the following would be the datasets that need to be created.

  • USER.INST001.RECV
  • USER.INST001.JCL
  • USER.INST001.CONF
  • USER.INST001.ZIP

The required dataset attributes are as follows:

Name Type RECFM LRECL BLKSIZE SIZE
RECV Sequential FB 80 3120 see below
JCL PDS FB 80 3120  
CONF PDS VB 508 512  
ZIP Sequential VB 16380 16384 see below

These local files will be located in the directory where the wizard was started.

XMIT File: AdabasSOAGateway/zOS/ASG.XMIT
ZIP File: AdabasSOAGateway/zOS/asg.zip

The size attribute for the RECV and ZIP datasets to be created on the zOS should be calculated as follows:

RECV File: Divide the size of ASG.XMIT in bytes by 3120. Round the resultant size upwards to the nearest integer to obtain the file size in blocks. We recommend a size of 9700 blocks.

ZIP File: Divide the size of asg.zip in bytes by 16380. Round the resultant size upwards to the nearest integer to obtain the file size in blocks. We recommend a size of 700 blocks.

After having transfered the files using the Depl,oyment Wizard the datasets will contain the following

RECV   Sequential file containing the Portus load modules. This will be TSO RECEIVEd as part of the installation process.
JCL SOAGINS1 A job to perform a TSO receive.
  SOAGINS2 A job which deletes, creates, initializes, and unzips the Portusfile system into the file system available to Apache in this environment. The DEL step of this job will finish with CC=8 if the PFS dataset does not exist. Likewise, if the PFS dataset does exist, it will be deleted by this job.
  SOAGINS3 A job which copies a Apache's configuration file from a PDS member to the PortusEnvironment.
  SOAGINS4 A job which copies the license file the SOA Gateway Environment.
  SOAGPROC PROC to be used for running all other jobs.
  SOAGSTRT Job which starts the Portus Server.
  PFSPROC PROC to be used for various utilities.
  CPLOGS A job which copies Apache's error_log to an OUTPUT DDCARD if a failure occurs during Portusinitialization. Once the Portusserver is initialized, this log will be written to the JES Spool.
  PFSLS A job which lists the contents of the Portusfile system.
  CLIINI A DB2 CLI Initialization File. If using DB2 Driver this will need to be modified to reflect the Sub-System ID and location name. Your DBA can provide this information.
CONF CONFIG File used by Portusto declare environment variables
  HTCONF A copy of the Portus Apache configuration file. This can be edited and copied into the Portus file system using SOAGINS3.
  GROUP Run-time configuration file
  HOSTS Run-time configuration file
  PASSWD Run-time configuration file
  DXRTRACE Run-time parameters for debugging. Only to be used at the direction of support
  DDCARD Adabas Run parameters
  SYSPARM Run-time parameters.
  ASGLIC License File.
ZIP   A Sequential zip-file containing the Portus file system.

If you do not wish to install the Portus (Eclipse) Control Centre, proceed to z/OS Server Setup

You can either, logon to the z/OS host and setup the Portus Server, or install the client pieces now (if selected) and run the server setup at a later time.

Submitting JCL and Starting Server

Review and modify the following jobs prior to submitting them to reflect your installation standards and the names of the datasets created during your installation.

  1. Review and submit SOAGINS1 to TSO RECEIVE the Portus load library.
  2. Review and submit SOAGINS2 to create, init, and populate the Portus file system.
  3. Review and submit SOAGINS3 to copy the Apache configuration file into the Portus filesystem.
  4. Review and submit SOAGINS4 to copy the Portus license into the Portus filesystem.
  5. If using the Adabas Driver review the DDCARD member and specify the correct Adabas SVC number. Under certain circumstances, the Adabas link routines may not pick up the SVC and DBID values specified via DDCARD. In this case the SVC number and Database Id must be zapped into ADALNKR, as described in the Adabas installation documentation, and the modified ADALNKR made available in a STEPLIB library ahead of the one containing the original, unzapped version.
  6. If using the DB2/ODBC Driver review the CLIINI member and specify the correct MVSDEFAULTSSID and Location name.

    Refer to you DBA for this information.

  7. Submit SOAGSTRT to bring up the Portus (Apache) server. The server is ready to be used when you see the "XMiddLe ... is ready for requests" message in the XMIDCARD DD.

    Note: Restarting and stopping Portus: Due to the nature of the z/OS Apache configuration it is not possible to restart the server with a single command. The server must be stopped with "/p jobName" and started by submitting SOAGSTRT again. In this scenario, Apache may issue a warning about the httpd.pid being overwritten. This warning can safely be ignored.
  8. If the Portus Server is to be run as a started task (STC), copy SOAGSTRT to a procedure library.

Starting the Server with HTTPS support

To enable HTTPS connections, a sample SSL certificate and SSL sample key have been provided. These are for development only, and should not be used in a production environment.

  1. If you wish the server to listen on a non-default HTTPS port, review ...CONF(SSLCONF) and change all instances of 443 to the port you wish to listen for HTTPS connections.
  2. Edit the ...CONF(HTCONF) member and uncomment the Include conf/extra/httpd-ssl.conf directive
  3. Ensure the server has been stopped
  4. Review and submit SOAGINS5 to copy SSLCONF into the Portus file system.
  5. Review and submit SOAGINS3 to copy HTCONF into the Portus file system.
  6. Edit SOAGPROC and change the server parameters to -X -DSSL

    E.g. EXEC PGM=HTTPD,PARM='-X -DSSL',REGION=0M

  7. Submit SOAGSTRT to bring up the Portus (Apache) server. The server is ready to be used when you see the "XMiddLe ... is ready for requests" message in the XMIDCARD DD.

    HTTPS access can be tested by checking (change host and the HTTPS port to suit your system)

    https://myServer:8443/SoaGatewayStatus

For more information on configuring Apache for HTTPS see here


Ostia
www.ostiasolutions.com
Copyright @ 2006-2018 Ostia Software Solutions Limited.