Manually Upgrading BEA eLink OSI TP to Version 4.0

 

If you are upgrading from a previous version of eLink OSI TP to Version 4.0, you must modify your existing DMCONFIG file to create a UDMCONFIG file after installing eLink OSI TP.

Note: It is recommended that you use the osiadmin utility to upgrade your files, but you may perform this upgrade manually. Refer to the IMPORTCFG parameter in Using the OSI TP Administration Utility for more information about upgrading automatically.

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

• General Checklist for Manually Upgrading Your DMCONFIG File

• Step 1 - Backup Existing Configuration Files

• Step 2 - Copy DMCONFIG.TXT to UDMCONFIG.TXT

• Step 3 - Modify Parameters in the UDMCONFIG File

 

---

General Checklist for Manually Upgrading Your DMCONFIG File

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

1. After installing eLink OSI TP 4.0 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. Copy the existing DMCONFIG file to a new file named for example, UDMCONFIG.TXT.

3. Modify the UDMCONFIG file.

Following are the detailed steps for upgrading your UDMCONFIG 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. Additionally, OSI TP 4.0 provides a utility, udmloadcf, that processes your new configuration file, UDMCONFIG.TXT, and creates a DMCONFIG file. 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 - Copy DMCONFIG.TXT to UDMCONFIG.TXT

The udmloadcf utility, provided with OSI TP 4.0, processes your new configuration file, UDMCONFIG.TXT, and creates a DMCONFIG file. Copy your original DMCONFIG.TXT file to a new file called UDMCONFIG.TXT. This is the configuration file you will edit for the remaining steps. Enter the following command from your command line or DOS prompt to copy your DMCONFIG.TXT file to UDMCONFIG.TXT:

copy DMCONFIG.TXT UDMCONFIG.TXT

 

---

Step 3 - Modify Parameters in the UDMCONFIG 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.0, 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 UDMCONFIG 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
	REM_TPSUT	New
	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
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 UDMCONFIG File for more information about these new parameters.