Describes the
Enterprise Server requirements for deploying a service interface.
Restriction: This topic applies to Windows environments (local development) only.
Before deploying a service interface, ensure that each of these items has been addressed:
- Your enterprise server region must be configured for mainframe subsystem support and the type of service you are deploying to it.
- Your
enterprise server region must be started before deployment.
- If your
enterprise server region runs in 64-bit, and you deploy from a Windows 32-bit system, then the service driver program is not compiled and the compiled service driver program is not included in the deployment package. However, the COBOL source for the service driver program is always included in the deployment package. You must recompile the COBOL source for 64-bit; then copy the compiled program to the
enterprise server region. See
Compiling Native COBOL Programs for 64-Bit for more information.
- If your
enterprise server region is running on a remote UNIX installation of
Enterprise Server, you can still deploy to that enterprise server; however:
- For CICS and IMS service interfaces, this requires that you install
Enterprise Developer such that it is licensed to compile and run CICS and/or IMS applications.
- After you deploy, you must then compile the generated driver program for your service on the platform where
Enterprise Server is running. See
To compile a mainframe-based service driver program on a remote UNIX machine for instructions.