ZOSCONNECT

Difference between zos connect and zos connect beta

ZOSCONNECT ZOSCONNECT BETA

Key Component: Key Component :
1. Zos Connect 1. DOCKER Environment
2. Zos connect Server

Mode of creating API : Mode of creating API:

1. In ECLIPSE (IDZ)
2. Installing Zos Connect EE
Open API Support:
1. Open API 2 ( We used
Swagger UI for testing the API
locally)
2.It helps to import API easily such
as IBM API Connect
1. ZOS Connect Designer ( In
browser) with docker running in
background
Open API Support:
1.Open API 3.0 (Here we are
predefining the open API
definition before designing it. )
2. Open API Definition contains
meta information like API title,
version and etc.
 ZOSCONNECT
METHOD OF CREATING API :
1. Create a Service Project
2. Create a API Project in API
editor
3. Mapping the Request and
Response data
4. Build the API
5. Testing it through Swagger
6. Testing it in browser for
different
methods(GET,POST,PUT,DELE
TE)
ZOSCONNECT BETA
METHOD OF CREATING API
1. First we need to ensure that
docker is running on our
workstation
2. Downloading the ZOSConnect
designer image is downloaded
3. Instantiate our Container,
Change the ZCWorkspace
directory and run the command-
docker compose up –d -> this
command starts a container and
loads the ZOSCONNECT
Designer image
4. Open the ZOS Connect
designer UI in your browser
5. Import screen for OPEN API is
displayed , importing it. This open
API is written either in YAML or
ZOSCONNECT ZOSCONNECT BETA

5. Import screen for OPEN API is

displayed , importing it. This open
API is written either in YAML or
JSON
6. Click Create API to create the
project. When processing is
Complete , the information page is
presented.
7. Exploring the Z/OS Connect
Designer Interface . Here we need
to add the paths that our API
exposes . Operation are the HTTP
methods that are used to
manipulate these paths ,such as
GET,POST,PUT , or DELETE
8. Create a zos Asset
ZOSCONNECT ZOSCONNECT BETA
9.STOPPing the ZOSCONNECT
DESIGNER with either Redhat
codeready workspace or docker
compose
10.Check your Z/OS connect API
project into source code
management
11.Build process pulls from SCM
and mounts API project onto
Z/OS connect server container
image
12.Built container image is stored
in image repository
13.Environment config is
injected, then the container
image is run in different stages of
the staging environment like test
environment ,UAT and
production environment.