Escolar Documentos
Profissional Documentos
Cultura Documentos
Overview
XML Publisher stores all the meta data and physical files for templates and data definition in BLOB
columns in its schema. It is therefore time consuming to manually download information from a
development instance to a test and then to a production environment especially if there are many
templates to manage.
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 datasources from one instance to
another.
Managing Metadata
Both templates and data definitions are stored in the database and we can use the FNDLOAD loader
to download the metadata for these objects and then upload them to another instance. The
FNDLOAD program needs a control file (lct) that the XML Publisher team have provided. Its
structure is as follows:
XDO_DS_DEFINITIONS – attributes for data source
| KEY APPLICATION_SHORT_NAME
| KEY DATA_SOURCE_CODE
|
X_TEMPLATES – attributes for templates
| KEY TMPL_APP_SHORT_NAME
| KEY TEMPLATE_CODE
|
X_TEMPLATE_FIELDS – template fields
| KEY FIELD_NAME
Usage
Download
Using this structure we could use the FNDLOAD program to download any XML Publisher object
from all data definitions and their associated templates to just an individual template file.
The FNDLOAD command takes the following format:
If we wanted to download all data definitions and templates for Accounts Receivable we would use:
To download the data definition (ARXCOBLX) and one of its associated templates (ARLETTER1)
from that datasource.
Upload
Now we have a file definition of the data definition and template meta data we can now upload this
data to any EBS instance. The FNDLOAD command is similar to before except we use the
UPLOAD switch.
If we wanted to upload all of our data definitions and templates we could use:
If we only wanted to load certain data definitions or templates we could use attributes similar to the
DOWNLOAD options
This command will upload all data definitions and templates from the AR application that appear in
our ldt file.
Usage
Download
Firstly you need to ensure you have setup your environment for your session ie setting APPL_TOP,
CLASSPATH, etc.
This mode will create the template or data files, one LDT file, one DRVX file and one log file.
Sample usage as follows:
% java oracle.apps.xdo.oa.util.XDOLoader \
DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION ap000sun:1521:apps115 \
-APPS_SHORT_NAME XDO \
-LCT_FILE ${XDO_TOP}/patch/115/import/xdotmpl.lct \
-DS_CODE XDODS1
In this mode the ldt file can then be used with the FNDLOAD utility to upload the metadata for te
downloaded templates.
Upload
UPLOAD usage :
The loader can be used before or after the FNDLOAD command. The files will be loaded with its
LOB_CODE, this will join to the main metadata loaded using the TEMPLATE_CODE or
DATA_SOURCE_CODE mapping to the LOB_CODE.