XML Map Commands

Loading/Deleting a Map

Oracle message maps are delivered and installed on the $APPLTOP directory. They are automatically loaded into the XML Gateway repository using the LoadMap program. A map can be deleted using the DeleteMap program.
If you modified an Oracle prebuilt message map or created a new message map using the Message Designer, these maps are saved on your local file system. Perform the following steps to load the maps into the XML Gateway repository for use by the XML Gateway Execution Engine:

1.    Move <mymap>.xgm file from the local file system to the middle tier. The apps.zip file containing the maps that were installed on the $APPLTOP is installed on the middle tier.

2.    Execute java LoadMap<DB username><DB password><Hostname>:<Port>:<SID><mymap.xgm> to load the message map into the XML Gateway repository. LoadMap will replace existing maps with the same name.

Example: java LoadMap User1 welcome ap999sun.us.oracle.com:1521:ORA1151<mymap.xgm>

Note: The LoadMap process will load a map if the map version is compatible with the engine version. The map version is stored in the <ECX_MAJOR_VERSION> and the <ECX_MINOR_VERSION> tags of the map file (.xgm). The engine version is stored in WF_RESOURCES. Maps are compatible with the engine if the major version is the same and the minor version is the same or lower.

A map can be deleted using the DeleteMap program as follows:

1.    Execute java DeleteMap <DB username><DB password><Hostname><:<Port>:<SID><mapcode> to delete a message map from the XML Gateway repository. LoadMap will replace existing maps with the same name, but obsolete maps with a different name must be deleted manually.

<mapcode> is the map name entered in the Message Designer.

Example: java DeleteMap User1 welcome ap222sun.us.oracle.com:1521:ORA1151<mapcode>

Loading and Deleting a DTD

Each message map is associated with a set of DTDs: the main and its reference DTDs. Similar to message maps, the DTDs associated with the Oracle prebuilt message maps are delivered and installed on the $APPLTOP. They are automatically loaded into the XML Gateway database using the LoadDTDToClob program. A DTD can be deleted using the DeleteDTDFromClob program.
To change a DTD referenced in an existing message map, use the File > Properties menu option of the Message Designer to make the necessary change. The updated message map must be loaded into the XML Gateway repository using LoadMap (refer to Loading/Deleting a Map). In addition, the new DTD used must be loaded into the XML Gateway database as follows:

1.    Move <mydtd>.dtd file from the local file system to the middle tier. The apps.zip file containing the DTDs that were installed on the $APPLTOP is on the middle tier.

2.    Execute java LoadDTDToClob<DB username><DB password><Hostname>:<Port>:<SID><mydtd.dtd> <RootElementName><Location> to load the DTD into the XML Gateway database. LoadDTDToClob will replace existing DTDs with the same name.

<RootElementName> is the XML Root Element entered in the Message Designer.

<Location> is the subdirectory name entered in the Specify XML File and Root Element window of the wizard.

A DTD can be deleted using the DeleteDTDFromClob program as follows:
Execute java DeleteDTDFromClob <DB username> <DB password> <Hostname>:<Port>:<SID><mydtd.dtd> <RootElementName><Location> to delete a DTD from the XML Gateway database. LoadDTDToClob will replace existing DTDs with the same name, but obsolete DTDs with a different name must be manually deleted.
<RootElementName> is the XML Root Element entered in the Message Designer.
<Location> is the subdirectory name entered in the Specify XML File and Root Element window of the wizard.
LoadMap and LoadDTDToClob are provided as two separate programs to support various combinations of changes. To ensure that the maps and DTDs are synchronized, always execute LoadMap and LoadDTDToClob as a pair.

Downloading a Map

You can download a map from the ECX table to produce the corresponding XGM file. Use the DownloadMap.java utility to download the map to the log directory.
The usage is as follows:
java DownloadMap <DB username><DB password><Hostname>:<Port>:<SID><MAP_CODE>
Note that there will be differences between the original map and the downloaded map.

Differences Between the Downloaded Map and the Original Map

The downloaded map and original map will differ as follows:

·         If the original map has a code category that is not present in ecx_xref_hdr, the downloaded map will not show the code category.

·         If the original map uses variables of data type other than VARCHAR2, CHAR, NUMBER, CLOB, or DATE, the download map will default it to VARCHAR2.

·         If the original map was created with a Message Designer version other than 2.6.0.X, the DownloadMap utility will default it to 2.6.3.0.0.

·         If the original map was created with a version of Message Designer that did not include the dbdrv hints, these hints will be present in the downloaded map.

Steps to Load Custom Map

Command to load the Custom map manually into the repository using the below XML Gateway Map loader. 

Run the following command, from the APPL_TOP.

$ java oracle.apps.ecx.loader.LoadMap <uname> <passwd> <host:port:sid> xx_cXML_OrderRequest.xgm

Steps to Delete Custom Maps:

Please run the below command to delete the Custom Map in BNPSIT

$ java oracle.apps.ecx.loader.DeleteMap <uname> <passwd> <host:port:sid> xx_cXML_OrderRequest.xgm

Steps to Load DTD Manually

Log on applmgr

  - cd $PO_TOP/xml/cXML12007

  - java oracle.apps.ecx.loader.LoadDTDToClob apps apps <hostname>:<port>:<SID> cXML.dtd cXML po/xml/cXML12007

  Note: Bounce the entire Workflow Agent Listener Service