Creating a z/OS Connect (OpenAPI 2) server
Use the zosconnect command to create an IBM z/OS Connect server.
Before you begin
To use the zosconnect command, you must be an IBM z/OS Connect administrator with access to the OMVS shell.
Before you create an IBM z/OS Connect server, ensure that the shared directory is available. For more information, see Creating the IBM z/OS Connect shared directory.
For step-by-step examples of creating a server and connecting it to a System of Record (SoR),
see:
About this task
This task shows you how to use the default template to create an IBM z/OS Connect server. Templates are a Liberty feature
that you can use when you create a server. Other service providers can supply their own templates to
enable a quicker start with their functions. For more information, see Creating Liberty servers from custom configurations in the
WebSphere® Application Server Liberty
documentation.
Note: The file permissions on the server are controlled by setting the
_BPX_BATCH_UMASK STDENV
variable. For more information, see
_BPX_BATCH_UMASK
environment variables in the z/OS UNIX System Service
documentation. IBM z/OS Connect server does not use
the umask settings in /etc/profile and user’s
.profile files.Procedure
Results
The following table shows the directory structure and
contents when a server is created:
Path | Contents |
---|---|
<WLP_USER_DIR>/servers | Server instances. One subdirectory per server instance, each created by using the create option of the zosconnect command. |
<WLP_USER_DIR>/extension | The location where user features are installed. |