> User Guide > Manually Upgrading to BEA Tuxedo Mainframe Adapter for OSI TP 9.1

User Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Manually Upgrading to BEA Tuxedo Mainframe Adapter for OSI TP 9.1

This section covers the following topics for manually upgrading your product:

 

Upgrading From eLink OSI TP Version 1.3

To manually upgrade your DMCONFIG file for TMA OSI TP Version 9.1, perform the following General Checklist steps. Each step is detailed in the following sections.

  1. After installing BEA Tuxedo Mainframe Adapter for OSI TP 9.1, locate the original DMCONFIG file, referred to as DMCONFIG.TXT, and the ositp configfile you wish to upgrade and make backup copies of the files before making any modifications.
  2. Modify the DMCONFIG file.

Following are the detailed steps for upgrading your DMCONFIG file:

 

Step 1 - Backup Existing Configuration Files

It is recommended that you make a backup copy of your original DMCONFIG.TXT file and OSITP CONFIGFILE before making any changes or running any utilities. A backup helps prevent the loss of your current configuration and allows you to restore any information in the event there is a problem. Enter the following command from your command line or DOS prompt to copy your DMCONFIG.TXT file to DMCONFIG.bak: 

copy DMCONFIG.TXT DMCONFIG.bak

 

Step 2 - Modify Parameters in the DMCONFIG File

You must change the DM_OSITP section name to DM_OSITPX, and you must modify the TYPE field in the DM_LOCAL_DOMAINS and DM_REMOTE_DOMAINS sections to be TYPE=OSITPX. In order to use some of the newer features, you may optionally want to modify the DM_LOCAL_SERVICES and DM_REMOTE_SERVICES definitions as well. Changes to each of these sections consist of removing obsolete parameters, adding new parameters, and modifying values for existing parameters. You can modify entries in the DMCONFIG file using any text editor.

Following is a summary of the changes that need to be made to your configuration:

Section
Parameter
Change
DM_OSITP
 
Obsolete
DM_OSITPX
 
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
DM_OSITPX
ACN
Obsolete
 
AEID
Obsolete
 
AEQ
Obsolete
 
AET
Now required for each domain
 
APID
Obsolete
 
APT
Obsolete
 
DNS_RESOLUTION
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
MAX_LISTENING_EP
Obsolete
 
NWADDR
Now required for each domain
 
NWDEVICE
Obsolete
 
OPTIONS
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
P_SEL
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
PROFILE
Obsolete
 
S_SEL
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
T_SEL
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
TAILOR_PATH
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
URCH
Obsolete
DM_LOCAL_DOMAINS
SECURITY
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
TYPE=OSITP
Obsolete
 
TYPE=OSITPX
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
DM_LOCAL_SERVICES
COUPLING
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
INRECTYPE
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
OUTRECTYPE
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
DM_REMOTE_DOMAINS
TYPE=OSITP
Obsolete
 
TYPE=OSITPX
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
CODEPAGE
 
Available in eLink OSI TP 4.1, 4.2 and TMA OSI TP 8.1 and 9.1
DM_REMOTE_SERVICES
AUTOPREPARE
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
INRECTYPE
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
OUTRECTYPE
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
REM_TPSUT
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1
 
TPSUT_TYPE (must be specified BEFORE REM_TPSUT)
Available in eLink OSI TP 4.x and TMA OSI TP 8.1 and 9.1

Refer to Understanding the DMCONFIG File for more information about these new parameters.

 

Upgrading From eLink OSI TP Version 4.0

There are no changes required to the eLink OSI TP 4.0 UDMCONFIG input file. Perform a dmloadcf of this file to create a BDMCONFIG binary file compatible with Tuxedo 9.0 or 9.1. If your ubbconfig file contains eLink OSI TP 4.0 Administrative Server UDMADM, which is obsolete for TMA OSI TP 9.1, delete it and perform a tmloadcf of the modified ubbconfig.


  Back to Top       Previous  Next