Before you can run and test an OS 2200 Open DTP ePortal application, you must properly configure both the ePortal application and the OSI-TP software on the OS 2200 server.
This section provides some configuration guidelines. For more details, consult the following:
For details on configuring OSI-TP on the OS 2200 server, refer to the OS 2200 OSI-TP High-Performance Transaction Processing for XATMI (HTP/x) Implementation and Administration Guide.
For details on configuring an OS 2200 Open DTP ePortal presentation application, refer to ePortal Application Configuration Property Values.
The OSI-TP Configuration on the OS 2200 Server
The OSI-TP configuration on the OS 2200 server consists of the elements config/in and tailor/in.
The config/in element includes an entry to describe each Application Entity (AE). An AE represents a node in your OSI-TP network.
There is one AE to represent the OSI-TP software running on the OS 2200 server. This AE must be identified by the MLOCAL statement in the tailor/in element. Therefore, this AE is referred to as the MLOCAL AE in this document.
In addition, each concurrent instance of an OS 2200 Open DTP ePortal presentation application is also an AE in the OSI-TP network. Therefore, each concurrent instance of an OS 2200 Open DTP ePortal presentation application must have an entry in the OSI-TP config/in element on the OS 2200 server. Each of these AEs is referred to as an ePortal AE in this document.
Each entry in the config/in element specifies the following information for one AE:
AE alias – a unique 1 to 16 character name to represent the AE. This name can include letters, digits, and hyphens only. For example: MY-2200HOST
AE Title – A dotted integer identifier that uniquely defines the AE. The first integer is 0, 1, or 2. The second integer is 0 thru 39. The remaining integers are user defined. For example: 1.3.192.168.223.250.2476.
TCP/IP Address(es) – This represents one or more network addresses for the AE. Each address is of the form <ip-address>:<port>, where <ip-address> is the Domain Name Server name or IP Address and <port> is the TCP port number. The port number must be in the range 1 through 65535 inclusive. The default port for OSI-TP is 2476.
Notes:
The MLOCAL AE should specify at least two addresses:
One address is the public address which is used for development testing. This address uses a network address which is on the public LAN. For example, myhost.mycompany.com:2476.
One address is the private backend address used to connect the ePortal appliance to the OS 2200 server. This address defaults to 192.168.223.250:2476.
An ePortal AE does not need a TCP/IP address. Therefore, you configure the value 0.0.0.0:1 for an ePortal AE.
When you configure your OS 2200 Open DTP ePortal presentation application, ePortal automatically generates text files to help you configure OSI-TP on the OS 2200 server. Refer to the next section for more information.
The OS 2200 Open DTP ePortal Presentation Application Configuration
To configure your OS 2200 Open DTP ePortal presentation application, refer to Viewing or Changing ePortal Application Configuration Properties and ePortal Application Configuration Property Values.
When you configure your OS 2200 Open DTP ePortal presentation application, ePortal creates the following text files to help you configure OSI-TP on the OS 2200 server:
dataSourceName.configin – This file represents a sample OSI-TP config/in element which matches the values you configured for your presentation project.
dataSourceName.tailorin – This file represents a sample OSI-TP tailor/in element which matches the values you configured for your presentation project.
These files are generated in the root directory for the OS 2200 Open DTP ePortal presentation project. These files are not part of the Visual Studio project; therefore, to view these files using Visual Studio, do the following:
Open the Solution Explorer.
Click on the toolbar button Show All Files in the Solution Explorer.
Double-click the file in the Solution Explorer.
You should copy these files to your OS 2200 server. To copy these files, you can use Secure File Transfer Protocol (SFTP) or you can use Common Internet File System (CIFS) to map to a share from an OS 2200 server. Refer to the CIFS for ClearPath OS 2200 User, Programmer, and Administrator Reference Manual.
If you have an existing OSI-TP configuration, you should merge the entries in the <dataSourceName>.configin file into your existing config/in element. Similarly, you should merge the entries in the <dataSourceName>.tailorin file into your existing tailor/in element.
Refer to the comments in the generated files for more information.