OSC System Settings

Before the OSC system can be started, the system environment must be properly configured. This can be done by editing the OSC and Tmax configuration files.

1. OSC Configuration

To run OSC, the OpenFrame configuration files must be properly set up. The files contain information about OpenFrame system, application server and OSC TDQ Log server.

  • OSC Configuration File

    The following describes the OSC configuration file. For further details, refer to the description of each respective section.

    Configuration File Description

    ofsys.seq

    Contains server names of other OpenFrame system servers such as OpenFrame/Base and Batch by line. This file is used for system startup and shutdown.

    ofosc.seq

    Contains OSC user server names by line when servers such as OSCMQSVR are used. This file is used for system startup and shutdown.

    osc.region.list

    Contains OSC region names. This file is used for system startup and shutdown.

  • OSC Configuration

    Configuration for OSC operation is set to the 'KEY' of each 'SECTION' in the openframe_osc.conf file. After that, the system settings are saved by using the ofconfig tool.

    The following describes each subject.

    Subject Description

    cobnet

    Configures items used in the cobnet server to support invoking COBOL applications from .NET applications.

    osc

    Configures common information for OSC systems.

    osc.{servername}

    Configures items used in OSC application servers.

    osc.{osctlsvrname}

    Configures items used in the TDQ log server when using the log-type TDQ in OSC Region.

    osc.{oscmqsvrname}

    Configures items used in servers provided for Queue Trigger Monitor by IBM Webshphere MQ.

For more information about subjects and settings for configurations, refer to OpenFrame Configuration.

1.1. ofsys.seq

The ofsys.seq file contains OpenFrame system server names and is used for OSC system startup and shutdown. The OSC system servers are started sequentially according to this file, and shut down in reverse order to how they were started.

The following is an example of ofsys.seq that specifies OpenFrame system servers named ofrlmsvr, ofrlmwrk, and ofrsmlog.

ofrlmsvr
ofrlmwrk
ofrsmlog

1.2. ofosc.seq

The ofosc.seq file contains OSC user server names and is used for OSC system startup and shutdown. For example, OSCMQSVR can be specified. The OSC system servers are started sequentially according to this file, and are shut down in reverse order to how they were started.

The following is an example of ofosc.seq that specifies OSC user servers named OSCMQ001.

OSCMQ001

1.3. osc.region.list

The osc.region.list file contains OSC region names and is used for OSC system startup and shutdown. The OSC system servers are started sequentially according to this file, and are shut down in reverse order of how they were started.

The following is an example of osc.region.list that specifies OSC regions named OSC00001 and OSC00002.

OSC00001
OSC00002

2. Tmax Configuration File

The OSC system is built around Tmax. Therefore, in order for OSC to operate normally, a number of servers and services must be set up in the Tmax configuration files.

The OSC servers are divided into application servers, auxiliary servers, user servers, and system servers. The settings in the Tmax configuration files for the application and auxiliary servers will vary according to the setup of the user’s regions, and the settings for the user servers will vary according to the user’s system configuration. However, those for the OSC system servers are always the same, regardless of the user’s region formation.

This section describes how to set Tmax configuration files for the OSC system and user servers.

For more information on the OSC application server and auxiliary server settings for each region, refer to Setting Tmax Configuration File.

2.1. Server Group Settings

The [SVRGROUP] section defines two server groups - svgotpn and svgotpb - with settings that vary according to the OSC system server’s type. In a single-node environment, all server groups have the same settings, but in a multi-node environment, the COUSIN, BACKUP, and LOAD settings will vary according to each group’s characteristics.

The two server groups are described as follows:

Group Name Description

svgotpn

Does not support load balancing or backup in a multi-node environment.

svgotpb

Supports backup between nodes but not load balancing.

The following is an example of the [SVRGROUP] section set up for a single-node environment.

*SVRGROUP
svgotpn         NODENAME = "NODE1"
svgotpb         NODENAME = "NODE1"

The following is an example of the [SVRGROUP] section set up for a multi-node environment consisting of NODE1 and NODE2.

*SVRGROUP
svgotpn         NODENAME = "NODE1", COUSIN = svgotpn2, LOAD = -1
svgotpn2        NODENAME = "NODE2", LOAD = -1
svgotpb         NODENAME = "NODE1", BACKUP = svgotpb2
svgotpb2        NODENAME = "NODE2"

2.2. System Server Settings

The [SERVER] section registers the OSC system servers. There are seven servers that need to be registered: oscmcsvr, oscadsvr, oscmnsvr, oscncsvr, oscsdsvr, and oscdfsvr.

The [SERVER] section must be set up as follows, regardless of the organization of nodes and regions.

*SERVER
oscmgr           SVGNAME = svgotpn, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscmcsvr         SVGNAME = svgotpn,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscmnsvr         SVGNAME = svgotpn, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscncsvr         SVGNAME = svgotpb, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscscsvr         SVGNAME = svgotpb, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscdfsvr         SVGNAME = svgotpb, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"
oscjcsvr         SVGNAME = svgotpb, MAX = 1, SVRTYPE = UCS,
                 CLOPT = "-o $(SVR).out -e $(SVR).err"

2.3. System Server Service Settings

The [SERVICE] section registers the services required by OSC system servers.

The [SERVICE] section must be set up as follows, regardless of the organization of nodes and regions.

*SERVICE
# oscmgr
OSCMGRSVC       SVRNAME = oscmgr
OSCMGRREGLIST   SVRNAME = oscmgr
OSCMGRTERMLIST  SVRNAME = oscmgr
OSCMGRDISCONN   SVRNAME = oscmgr
OSCMGRHOURGLASS SVRNAME = oscmgr

# oscmcsvr
OSCMCSVRSMFW    SVRNAME = oscmcsvr

# oscncsvr
OSCNCSVRDEFINE  SVRNAME = oscncsvr
OSCNCSVRDELETE  SVRNAME = oscncsvr
OSCNCSVRGET     SVRNAME = oscncsvr
OSCNCSVRQUERY   SVRNAME = oscncsvr
OSCNCSVRREWIND  SVRNAME = oscncsvr
OSCNCSVRUPDATE  SVRNAME = oscncsvr
OSCNCSVRBROWSE  SVRNAME = oscncsvr

# oscscsvr
OSCSCSVRSTART   SVRNAME = oscscsvr
OSCSCSVRDELAY   SVRNAME = oscscsvr
OSCSCSVRCANCEL  SVRNAME = oscscsvr
OSCSCSVRINFO    SVRNAME = oscscsvr
OSCSCSVRCONTROL SVRNAME = oscscsvr

# oscdfsvr
OSCDFSVRBRKE    SVRNAME = oscdfsvr
OSCDFSVRBRIN    SVRNAME = oscdfsvr
OSCDFSVRCHCK    SVRNAME = oscdfsvr
OSCDFSVRRESP    SVRNAME = oscdfsvr
OSCDFSVRREIN    SVRNAME = oscdfsvr
OSCDFSVRSETF    SVRNAME = oscdfsvr

# oscdfsvr
OSCJCSVRFLUSH   SVRNAME = oscjcsvr
OSCJCSVRWRITE   SVRNAME = oscjcsvr

2.4. User Server Settings

The [SERVER] section registers OSC user servers, which are the oscmqsvr server.

The following is an example of the [SERVER] section. Settings for servers can be different depending on node configuration. This example sets the oscmqsvr named OSCMQ001.

*SERVER
OSCMQ001      SVGNAME = svgotpu, TARGET = oscmqsvr, MAX = 1, SVRTYPE = UCS,
              CLOPT = "-o $(SVR).out -e $(SVR).err -n"

3. TCache Configuration

For multi-node clustering functionality, information that require sharing between RTSD and application servers are managed in a DB table. When viewing a table with infrequent updates, TCache is used, which minimizes performance degradation from DB usage.

TCache needs to be configured by individual node. Configure a shared memory key and table information for each region.

For more information about TCache configuration, refer to Tmax TCache Guide..

4. WAS Servlet Configuration

When sending an external request to OSC, data can be processed and delivered by deploying an OSC application in Web Application Server (WAS). For example, if an external client sends an HTTP protocol request to OSC, it is delivered to OSC through WAS.

The following describes how to configure WAS servlets used when sending requests to OSC server.

4.1. oschttp

oschttp is a servlet that processes data to send an external HTTP request to OSC.

Installing OSC creates servlet files and necessary settings under the following directory. To use them, you must manually deploy them in the WAS in use.

$OPENFRAME_HOME/osc/oschttp/

For information about how to deploy resources in WAS, refer to the respective guide of the WAS.
oschttp.properties

oschttp.properties sets information about OSC to which a request is sent.

TMAXIP = tmax_ip
TMAXPORT = tmax_port
ENDIAN = [BIG_ENDIAN | LITTLE_ENDIAN]
REGIONNAME = region_name
TCLNAME = tranclass_name

The following describes each item.

Item Description

TMAXIP

Tmax IP address of OSC to send the request to.

TMAXPORT

Tmax port number of OSC to send the request to.

ENDIAN

ENDIAN corresponding to OS of OSC.

REGIONNAME

Region name of OSC to send the request to.

TCLNAME

Tranclass name of OSC to send the request to.

The following is an example of oschttp.properties.

TMAXIP = 192.168.190.129
TMAXPORT = 8888
ENDIAN = BIG_ENDIAN
REGIONNAME = OSC00001
TCLNAME = TCL1