Version 9.5 SP1
 —  EntireX BS2000/OSD Batch RPC Server  —

Deploment Service under BS2000/OSD

This document covers the following topics:


Introduction

The deployment service

graphics/deploymentService.png

Top of page

Scope

The deployment service is used for the

See Server Mapping Deployment Wizard.

The deployment service uses the same class and server names as defined for the EntireX RPC server, and DEPLOYMENT as the service name, resulting in class/server/DEPLOYMENT as the broker service. Please note DEPLOYMENT is a service name reserved by Software AG. See broker attribute SERVICE.

Top of page

Enabling the Deployment Service

Start of instruction setTo enable the deployment service

  1. For a BS2000/OSD Batch RPC Server, the server mapping file ISAM (container) must be installed and configured. See Step 1: Define an RPC SVM File.

  2. Set the RPC server parameter deployment=yes. See deployment under Configuring the RPC Server.

  3. Define in the broker attribute file, under the RPC service, an additional broker service with DEPLOYMENT as the service name and values for class and server identical to those used for the RPC service. For example, if your RPC service is named

    CLASS = RPC    SERVER = SRV1    SERVICE = CALLNAT

    the deployment service requires the following additional service definition in the broker attribute file:

    CLASS = RPC    SERVER = SRV1    SERVICE = DEPLOYMENT
  4. Optional. If you need to restrict the use of the deployment service to a selected group of users, use EntireX Security and define security rules for the class/server/DEPLOYMENT broker service. The service name DEPLOYMENT is a constant.

Top of page

Disabling the Deployment Service

Start of instruction setTo disable the deployment service

Top of page