Craig,
We use the Z/OS Connect toolkit – running on a PC or server to generate a API or SERVICE. This stuff is stored in a PROJECT, basically a Directory on your PC containing various files, XML etc,
For example
cics-px-ping is an API project, and pxping is a SERVICE project:
The cics-px-ping.aar and the pxping.sar are in effect the executables which are deployed to the Z/OS Connect server running on the mainframe. So a SERVICE is basically initiating a IMS or CICS program which we currently have under Endevor management. But in this new world we need to store the entire project (service or api) also under endevor – as this is essentially the source code. So we can export
a project into a zip file – and our thinking is to store that in Endevor, and let an Endevor :
1. Get the Zip File
2. Look at the contents of the Zip
3. Find the .AAR or .SAR file
4. Deploy the .AAR or .SAR file to Z/OS Connect – basically copying this to a ZFS Directory on the server
5. Issuing a Refresh command to activate the service or api
So I’m asking the CA world out there of Endevor users also using Z/OS Connect for their experience in this area.
Thanks
Tony Shediak
Principal Infrastructure Specialist
Mainframe Services
Ground Floor
4-16 Montgomery Street
Kogarah, NSW, 2217
M +61 402 189 580
tshediak@westpac.com.au<mailto:tshediak@westpac.com.au>