Manually Upgrading BEA eLink OSI TP to Version 4.2


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Search \| PDF Files \| Contact

eLink OSI TP Doc Home \| User Guide \| Previous Topic \| Next Topic \| Contents \| Index \| View as PDF

If you are upgrading from am older version of eLink OSI TP to version 4.2, you must modify your existing DMCONFIG file to create a DMCONFIG file compatible with Tuxedo 8.

Note: It is recommended that you use the osiadmin utility to upgrade your DMCONFIG file, but you can perform this upgrade manually.

This section covers the following topics for manually upgrading your DMCONFIG file:

Upgrading From eLink OSI TP Version 1.3

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

After installing eLink OSI TP 4.2 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.
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 new features of OSI TP 4.2, 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		New
DM_OSITPX	ACN	Obsolete
	AEID	Obsolete
	AEQ	Obsolete
	AET	Now required for each domain
	APID	Obsolete
	APT	Obsolete
	DNS_RESOLUTION	New
	MAX_LISTENING_EP	Obsolete
	NWADDR	Now required for each domain
	NWDEVICE	Obsolete
	OPTIONS	New
	P_SEL	New
	PROFILE	Obsolete
	S_SEL	New
	T_SEL	New
	TAILOR_PATH	New
	URCH	Obsolete
DM_LOCAL_DOMAINS	SECURITY	New
	TYPE=OSITP	Obsolete
	TYPE=OSITPX	New
DM_LOCAL_SERVICES	COUPLING	New
	INRECTYPE	New
	OUTRECTYPE	New
DM_REMOTE_DOMAINS	TYPE=OSITP	Obsolete
	TYPE=OSITPX	New
CODEPAGE		New
DM_REMOTE_SERVICES	AUTOPREPARE	New
	INRECTYPE	New
	OUTRECTYPE	New
	REM_TPSUT	New
	TPSUT_TYPE (must be specified BEFORE REM_TPSUT)	New

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 8.0. If your ubbconfig file contains eLink OSI TP 4.0 Administrative Server UDMADM, which is obsolete for eLink OSI TP 4.1 and 4.2, delete it and perform a tmloadcf of the modified ubbconfig.