Moving Templates and Data Definitions Between E-Business Suite Instances

XML Publisher stores the metadata and physical files for templates and data definitions
in BLOB columns in its schema. During testing and development you commonly must
download information from a development instance to a test instance and then to a
production environment. This can be very time consuming, especially if there are many
templates to manage. To streamline this process, XML Publisher uses the FNDLOAD
loader technology and its own XDOLoader to allow you to move the metadata and
physical files for your templates and data definitions from one instance to another.

FNDLOAD:

Use FNDLOAD utility to upload and download the data definition information and
the template metadata stored in the Template Manager.
To load Data Definitions and Templates from tst1 instance to tst2 instance using FNDLOAD

---------------------------------------------------------------------------------------------------------
Step1:
tst1 - FNDLOAD apps/fnd@tst1 0 Y DOWNLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt XDO_DS_DEFINITIONS
APPLICATION_SHORT_NAME=CUSTOM DATA_SOURCE_CODE=SAIEMPXML

Step 2:
tst2 - FNDLOAD apps/fnd@tst2 0 Y UPLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt
Scenarios in which FNDLOAD can be used:
FNDLOAD can be used only in the following cases:

a)To move all the data definitions and templates metadata from a particular instance to another :
FNDLOAD apps/fnd@tst1 0 Y DOWNLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt XDO_DS_DEFINITIONS

b)To move all XDO metadata for a particular application such as CUSTOM .
tst1 - FNDLOAD apps/fnd@tst1 0 Y DOWNLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt XDO_DS_DEFINITIONS
APPLICATION_SHORT_NAME=CUSTOM

c) To move a single data definition (data source code =SAIEMPXML) and its associated templates:
FNDLOAD apps/fnd@tst1 0 Y DOWNLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt XDO_DS_DEFINITIONS
APPLICATION_SHORT_NAME=CUSTOM DATA_SOURCE_CODE=SAIEMPXML

d) To move a single data definition (data source code= SAIEMPXML) and a
specific template as follows:
FNDLOAD apps/fnd@tst1 0 Y DOWNLOAD
$XDO_TOP/patch/115/import/xdotmpl.lct XMLPData.ldt XDO_DS_DEFINITIONS
APPLICATION_SHORT_NAME=CUSTOM DATA_SOURCE_CODE=SAIEMPXML
TMPL_APP_SHORT_NAME=CUSTOM TEMPLATE_CODE= SAIEMPXML

Limitations:
1. FNDLOAD cannot be used to upload and download metadata between two
different servers.
2. FNDLOAD cannot be used to move metadata for two different applications such
as CUSTOM and AR at a time.
3. Also for a single application such as CUSTOM , we cannot specify more than one
data source code.

XDOLOADER Utility:
Use the XDOLoader utility to upload and download the physical files
(RTF, PDF, XSL-FO, XML, and XSD).
To transfer physical files such as RTF, RDF, XSL-FO from tst1 to tst2
------------------------------------------------------------------------------------------------------------
Step 1:
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD fnd \
-JDBC_CONNECTION sharp.apps.com:1522:tst1 \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME CUSTOM \
-LOB_CODE ZEMP \
-LANGUAGE en \
-TERRITORY US

Step2:
java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \
-DB_USERNAME apps \
Page 3 of 3
-DB_PASSWORD fnd \
-JDBC_CONNECTION sharp.apps.com:1521:tst2 \
-LOB_TYPE TEMPLATE_SOURCE \
-APPS_SHORT_NAME CUSTOM\
-LOB_CODE ZEMP \
-LANGUAGE en \
-TERRITORY US \
-XDO_FILE_TYPE RTF \
-FILE_CONTENT_TYPE ’application/rtf’ \
-FILE_NAME ZEMP_en_US.rtf \
-NLS_LANG ENGLISH_UNITED STATES.WE8ISO8859P1