Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Installing and Using TIBCO Service Gateway for Files : Configuring Service Gateway for Files

Configuring Service Gateway for Files
Configuring a Service Gateway for Files to Run on Open Systems
To configure a Service Gateway for Files for Open Systems, you must edit the following parameter files:
The parameter files will be located in the database directory in either %OS_ROOT on Windows or ${OS_ROOT} on Solaris if you share configuration files with the base TIBCO Object Service Broker for Open Systems, or in the directory you specified during the install if you do not share configuration files. Sample template files are provided in these directories (they have the extension .template).
If the parameter files already exist in your database directory, modify each file as required for installation. If the parameter files do not already exist, perform the following:
1.
2.
3.
Rename the files as appropriate to mon.prm, session.prm, or ee.prm.
See Also
TIBCO Object Service Broker Parameters for details about the Execution Environment parameters.
Sample Configuration
The following is a sample mon.prm file. This file is used by the osMon process which starts the Service Gateway for Files:
#mon.prm file: Sample Configuration
NAME=DEFAULT
SERVERS="2 FILEGATEWAYS"
DOB=S6LSDOBA
Explanations of the parameters in the sample mon.prm file:
SERVERS=”2 FILEGATEWAYS”
Two Service Gateway for Files will be started. The name supplied must match a NAME parameter in your session.prm file.
S6LSDOBA represents the Communications Identifier of the Data Object Broker your Service Gateway for Files will attach to.
The following sample session.prm file shows the session parameters you must set.
#session.prm file: Sample Configuration
NAME=FILEGATEWAYS
EENAME=FGSRVEE
SERVERID=FGSERVER
SERVERTYPE=PRS
DSIXFTYPE=LINE_SEPARATED_ASCII
 
Matches the value specified in the SERVERS parameter in your mon.prm file.
FGSRVEE represents an EE Name, which matches a NAME parameter in your ee.prm file.
The SERVERID parameter supplies the server ID of the Service Gateway for Files. (The corresponding z/OS parameter is PEERSERVERID).
Optional. The DSIXFTYPE parameter controls, among other things, whether EBCDIC-to-ASCII conversions will be made on IMP and EXP tables. LINE_SEPARATED_ASCII is the default value and is typically the value you will need for remote access from Z/OS to ordinary flat files in an Open Systems environment.
The following sample ee.prm file shows the necessary Execution Environment parameters.
#ee.prm: Sample Configuration
NAME=FGSRVEE
DOB=S6LSDOBA
MAXSESSION=20
 
Matches the value specified in the EENAME parameter in your session.prm file.
S6LSDOBA represents the Communications Identifier of the Data Object Broker your Service Gateway for Files will attach to.
Optional. The MAXSESSION parameter controls how many concurrent sessions will be started before another EE will be started.
Configuring a Service Gateway for Files to Run on z/OS
This section shows you how to configure Service Gateway for Files on z/OS through the Execution Environment parameters supplied to the Service Gateway for Files in the JCL that starts it.
See Also
TIBCO Object Service Broker Parameters for details about the Execution Environment parameters.
Preliminary Steps
Before starting the Service Gateway for Files, do the following:
1.
2.
Have your z/OS systems programmer APF authorize the library HLQNONV.INSTVER.AUTH in order to use TCP/IP or z/OS cross memory communications. The S6BRELAY DD statement in the sample JCL configures a TCP/IP path to your remote Data Object Broker.
3.
Run EECONFIG from HLQNONV.INSTVER.JCL. Before submitting job EECONFIG, be sure to specify a valid SVC number in the SVC parameter for members PARMNEE and PARMBAT, which are located in HLQNONV.INSTVER.CNTL.
Sample Configuration
The following sample JCL starts a Service Gateway for Files named FGSERVER, and connects to a Data Object Broker with a COMMID of S6LSDOBA.
//S6LSQQPP JOB (1),’FILE GATEWAY’,MSGCLASS=Y,TIME=1440
/*JOBPARM SYSAFF=*,TIME=1440
//REMSRVR EXEC PGM=S6BDR000,REGION=0M,TIME=1440
//STEPLIB DD DSN=HLQNONV.INSTVER.AUTH,DISP=SHR
//HRNEXTR DD DSN=HLQNONV.INSTVER.AUTH,DISP=SHR
//HRNIN DD *
PEERSERVERNUM=4,
TDS=S6LSDOBA,
PEERSERVERID=FGSERVER
/*
//* TCP/IP definitions to communicate with remote DOB
//S6BRELAY DD DISP=SHR,DSN=HLQNONV.SLQ.RELAYCFG
/*
See HLQNONV.INSTVER.JCL(FILEGTWY).
Include the following Execution Environment parameters in your JCL (these are shown with the values supplied for the sample JCL):
Specifies the number of instances of the Service Gateway for Files. Service Gateway for Files will occupy this number of inbound connections on the Data Object Broker.
Optional. If not specified, defaults to OSB9999 where 9999 is the suffix that represents that a four-digit number, starting at 0001, is to be used by the identifiers as they are assigned.
The communications identifier of the Data Object Broker. Corresponds to the node name in RELAYCFG when using TCP/IP communications.
This is mandatory for a Service Gateway for Files. If this is defaulted, Service Gateway for Files functionality will not be enabled. Note that the parameter PEERSERVERID specifies the server ID of a Service Gateway for Files on z/OS. In the Open Systems environment, the parameter to use is SERVERID.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved