The download site provides
· This read-me file
It gives details about the content of the other downloads. It is supplied in two versions:
· A plain text file (README.TXT )
· HTML format to view with a browser (readme.html) (This file)
· A white paper
‘WebSphere Application Server for OS/390 and z/OS Automation and High Availability Solution Based on System Automation for OS/390’ describes the basics of automating WebSphere Application Server for OS/390 and z/OS and provides details of a sample automation setup. It can be used as a guide to setup automation for a customer’s WebSphere Application Server environment. Two versions of the paper are provided:
· PDF format to view with Adobe Acrobat Reader (WAS-HA.pdf)
· HTML format to view with a browser (WAS-HA.htm plus all the supporting files in the WAS-HA_files folder)
· The sample Policy Database (PDB)
This is the PDB used in the sample setup. It contains the definition required for an SA/390 automation setup for WebSphere. It includes all the base system resources and the WebSphere Application Server related resources and their relationships. Also included are WebSphere MQSeries resources although they are not required for WebSphere Application Server. The PDB is supplied in three forms:
· As a plain text report ($RPTFLAT.txt). This may be most convenient if you have an existing PDB and you want to use cut and paste to include some of the WebSphere definitions.
· As an HTML formatted report ($RPTHTML.html) for convenient viewing with a browser.
· As a binary file (WAS401.bin). You can use this file to create a copy of the sample PDB on your z/OS system which you can adapt to you installation requirements using the SA OS/390 customization dialogs under ISPF. In this case you should
· download WAS401.bin from this site to your PC
· transfer the file to your z/OS system in binary format. The target dataset should have the following characteristics:
Organization . . . : PS
Record format . . . : FB
Record length . . . : 80
Block size . . . . : 6160
· run TSO RECEIVE INDSN(datasetname) where datasetname is the name of the dataset into which you transferred the PC file. (TSO RECEIVE will prompt you for the name of the dataset into which the PDB files will be received).
· Sample tools for WebSphere Application Server for OS/390 and z/OS administration automation
With these tools you can set up batch jobs which find and activate WebSphere conversations that have been produced through SMEUI. For details on how to use these tools, please refer to the white paper. Here we provide
· Two files that contain JCL (WASMNTJ1.job and WASMNTJ2.job). These jobs call OMVS shell scripts wasmnts1 and wasmnts2.
· Two files that contain OMVS shell scripts (wasmnts1.script and wasmnts2.script). These scripts call REXX EXECs wasmntr1 and wasmntr2.
· Two files that contain REXX EXECs (wasmntr1.exec and wasmntr2.exec). The first EXEC find all conversations which can be activated. The second EXEC should only be run if there is exactly one conversation to activate. It then activates this conversation.
You can download these files to your PC, adapt them to your environment and upload them to your z/OS system