| Warning |
|---|
OECN RPC based on USP is considered obsolete and unsupported. The SSDT recommends that ITC sites use OECN VXS /wiki/spaces/CTD/pages/623294 for OECN RPC services. This document is retained for historical purposes for sites still maintaining a USP installation. ITC continuing to use USP-based RPC services should not contact the SSDT for support. |
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
Important: OECN RPC based on USP is considered obsolete. The SSDT recommends that ITC sites use OECN VXS for OECN RPC services. This document is retained for historical purposes for sites still maintaining a USP installation.OECN State Software contains an RPC (Remote Procedure Call) service. The RPC service allows remote State Software contains an RPC (Remote Procedure Call) service. The RPC service allows remote client software (e.g. web applications) to make remote calls to standard OECN software routines via an XML interface. The primary purpose of the RPC service is to expose standard OECN software functions and business logic for use in web based or graphical user interfaces.
...
- OECN State Software
- OpenVMS/Alpha Version 7.3-2
- One of:
- USP (Universal Service Provider) Version 6.1
- OECN VXS /wiki/spaces/CTD/pages/623294 v2.2-0
OECN VXS
The remainder of this document discusses USP as the transport layer for the OECN RPC service. If you prefer an alternative to USP, you should skip this document and use OECN VXS. /wiki/spaces/CTD/pages/623294.
Universal Service Provider (USP)
...
The “As Is” license from HP does not provide any software support for the USP. As of July 2008, the SSDT no longer maintains a support contract with STABILIT. The SSDT will be attempt to provide support for USP to the OECN DA Sites using it with state software. However, sites having problems with USP will be encourage to switch to OECN VXS /wiki/spaces/CTD/pages/623294 when possible for OECN RPC.
...
Start the configuration process with:
| Code Block |
|---|
$ @OECN$:OECNRPC_CONFIG
|
See the following sections for more information about the operation of the configuration utility.
...
·Table 1 Minimal SETUPENV parameters
| Wiki Markup | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| HTML Table | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
EMIS Configuration
OECN RPC will also use SETUPENV to establish the EMIS logical context for multiple databases. This is done using the same OECN$EMIS_DBS file used by EMIS_SELECT. Therefore, sites using OECN RPC must establish the standard OECN$EMIS_DBS file to define the available databases.
...
Below is an example of a minimal OECN$SETUP.INI file suitable for OECN RPC. The example has been simplified to just the parameters required by OECN RPC. However, DA Sites are free to use other features of SETUPENV to set logicals depending on their configuration and other uses of SETUPENV. See the OECN System Managers Manual for more information regarding SETUPENV and the OECN$SETUP.INI file.
| Code Block |
|---|
! Define entry for District A
!
SECTION=DISTA
TYPE=DISTRICT
DESCRIPTION="District A"
LOGICAL=OECN$DTA,DKA100:[DISTA.DATA]
IDENTIFIER=”[DISTA,*]” ! UIC group of District A users
! Define entry for District B
!
SECTION=DISTB
TYPE=DISTRICT
DESCRIPTION="District B"
LOGICAL=OECN$DTA, DKA100:[DISTB.DATA]
IDENTIFIER=DISTB_BUSINESSOFFICE ! Identifier of District B Business Office users
IDENTIFIER=DISTB_SECRETARIES ! Identifier of District B Secretaries posting REQs
|
...
For SETUPENV used interactively, the default IDENTIFIER parameters is:
| Code Block |
|---|
IDENTIFIER=”[*,*]”
|
This allows all users to see the entry. For OECN RPC the default IDENTIFIER is:
| Code Block |
|---|
IDENTIFIER=OECN_SYSMAN
|
This restricts the entry to only OECN DAS personnel by default. This difference in behavior is intended as a security constraint to make it more difficult for remote network clients from discovering district databases inappropriately. It also reduces confusion on the remote client by preventing a user from attempting to select a district they do not have access to.
...