Oracle BI Publisher Blog

You have been working feverishly on your EBS instance. You have everything working in your test environment ... you have developed twenty shiny new and sparkly templates with all the bells and whistles your end users could ever wish for ... you're now ready for the big time in your production instance. How do you move all of those files and all that supporting metadata to the production instance? You're not going to type it all in again and manually load files, where's FNDLOAD?, wheres the file loader? Don't panic, its there ... its been there since 5.0 just not documented ... sorry.

There is FNLOAD support for moving meta data about and also support for moving those physical files, sample data, templates, schemas, data templates even translations. All but the last two are documented in the latest docs. Check out the 5.6.2 docs here you want Appendix B starting on page 401. The write up is pretty decent  I think. I have to admit that there are two missing pieces.

1. Data Templates - this is pretty straightforward. There is a new lob type called 'DATA_TEMPLATE' so its treated just like any other XMLP file object.

2. XLIFF Files - these are the translation files, again an xml format but they have their own loader called, surprisingly enough 'XLIFFLoader'. It's very similar to the XDOLoader, here's how to use it

 UPLOAD usage : % java oracle.apps.xdo.oa.util.XLIFFLoader UPLOAD 
 -DB_USERNAME <db_username> 
 -DB_PASSWORD <db_password> 
 -JDBC_CONNECTION <jdbc_con_string> 
 -APPS_SHORT_NAME <application_short_name> 
 -TEMPLATE_CODE <template_code> 
 -OWNER <owner> 
 -CUSTOM_MODE [FORCE|NOFORCE] 
 -FILE_NAME <file_name> 


 Parameter Name    Description 
 UPLOAD          : (Mandatory) The first parameter 
 DB_USERNAME     : (Mandatory) Database user name (ex: apps) 
 DB_PASSWORD     : (Mandatory) Database user password (ex: manager)
 JDBC_CONNETION  : (Mandatory) JDBC database connection string (e.g.: ap000sun:1521:dev115) 
 APPS_SHORT_NAME : (Mandatory) 3 letter Application short name (ex: XDO)
 TEMPLATE_CODE   : (Optional) XDO Template code, if not given, it should be indicated 
                   in the header section of the xliff.
 OWNER           : (Optional) Owner of the template. Default is "ORACLE"
 CUSTOM_MODE     : (Optional) [FORCE|NOFORCE] Whether force update, default is NOFORCE 
 FILE_NAME       : (Mandatory) Name of the file to be uploaded 

Heres a sample usage:

 % java oracle.apps.xdo.oa.util.XLIFFLoader 
 UPLOAD 
 -DB_USERNAME apps 
 -DB_PASSWORD apps 
 -JDBC_CONNECTION ap000sun:1521:apps115 
 -APPS_SHORT_NAME XDO 
 -FILE_NAME patch/115/publisher/templates/JA/XDOTMPL1_ja_JP.xlf
 



DOWNLOAD Usage : % java oracle.apps.xdo.oa.util.XLIFFLoader DOWNLOAD 
 -DB_USERNAME <db_username> 
 -DB_PASSWORD <db_password> 
 -JDBC_CONNECTION <jdbc_con_string> 
 -APPS_SHORT_NAME <application_short_name> 
 -DS_CODE <ds_code> 
 -TEMPLATE_CODE <lob_code> 
 -FILES_DIR <directory> 
 -SUMMARY_FILE <summary_file> 

Parameter Name     Description 
 DOWNLOAD        : (Mandatory) The first parameter
 DB_USERNAME     : (Mandatory) Database user name (ex: apps)
 DB_PASSWORD     : (Mandatory) Database user password (ex: manager)
 JDBC_CONNETION  : (Mandatory) JDBC database connection string (e.g.: ap000sun:1521:dev115)
 APPS_SHORT_NAME : (Optional) 3 letter Application short name (ex: XDO)
 DS_CODE         : (Optional) XDO Data Definition code
 TEMPLATE_CODE   : (Optional) XDO Template code
 FILES_DIR       : (Optional) Files will be downloaded to the given directory.
                    If not provided, files are placed in the current directory.
 SUMMARY_FILE    : (Optional) If provided, will generate an xml file containing list
                    of files downloaded. This should be the full path name of the target file
                   (not affected by FILES_DIR parameter). 

Heres a sample usage:

% java oracle.apps.xdo.oa.util.XLIFFLoader 
 DOWNLOAD 
 -DB_USERNAME apps 
 -DB_PASSWORD apps 
 -JDBC_CONNECTION ap000sun:1521:apps115 
 -APPS_SHORT_NAME XDO 
 -TEMPLATE_CODE XDOTMPL1  

So now you should have everything you need to move those templates, data templates, translations, etc from test to production. We will of course get all of the above into the doc as soon as we can. Happy Moving!