|Oracle E-Business Suite Desktop Integration Framework Developer's Guide|
Part Number E15877-02
This appendix covers the following topics:
You can use the Generic Loader (FNDLOAD) concurrent program to download integrator definitions from an Oracle E-Business Suite instance to a text file, and to upload integrator definitions from a text file to an Oracle E-Business Suite instance. For example, you can download an integrator definition from a development or test instance and upload it to a production instance. You can also download and store a text file representation of an integrator definition for source control purposes.
Use the bneintegrator.lct configuration file with the Generic Loader to load integrator definitions. The bneintegrator.lct file is located in the $BNE_TOP/patch/115/import/ directory.
The entity for this configuration file is BNE_INTEGRATORS. This entity includes the following sub-entities: BNE_QUERIES, BNE_PARAM_LISTS, BNE_COMPONENTS, BNE_SECURED_OBJECTS, and BNE_VIEWERS.
To download integrator definitions using the Generic Loader, specify the bneintegrator.lct configuration file, the name of an LDT file in which to save the downloaded data, and the BNE_INTEGRATORS entity. You can choose to download all integrators for an application, a single specific integrator, or two or more specific integrators.
To download all integrators for an application, specify the application short name for that application in the INTEGRATOR_ASN download parameter. For example:
$ FNDLOAD apps/apps 0 Y DOWNLOAD bneintegrator.lct bneintegrators.ldt BNE_INTEGRATORS INTEGRATOR_ASN=BNE
To download a single specific integrator, specify the application short name for that application in the INTEGRATOR_ASN download parameter and the internal name of the integrator in the INTEGRATOR_CODE download parameter. For example:
$ FNDLOAD apps/apps 0 Y DOWNLOAD bneintegrator.lct bneNewMsgs.ldt BNE_INTEGRATORS INTEGRATOR_ASN=BNE INTEGRATOR_CODE=FND_NEW_MESSAGES_INTG
To download two or more specific integrators, specify the application short name for that application in the INTEGRATOR_ASN download parameter and a list of the internal names of the integrators in the INTEGRATOR_CODE_LIST download parameter. The integrator internal names in the list should be separated by commas and should not include wildcards. For example:
$ FNDLOAD apps/apps 0 Y DOWNLOAD bneintegrator.lct bneNewMsgs.ldt BNE_INTEGRATORS INTEGRATOR_ASN=BNE INTEGRATOR_CODE_LIST=FND_NEW_MESSAGES_INTG,JOURNALS_115
Note: When you download integrators with the INTEGRATOR_CODE_LIST parameter, the Generic Loader may download any integrators whose internal names are substrings of the specified integrator internal names, in addition to the specified integrators. For example, if you specify INTEGRATOR_CODE_LIST=XYZ_INTEG01,XYZ_INTEG02, the Generic Loader may download integrators named XYZ_INTEG and XYZ_INT as well as the integrators XYZ_INTEG01 and XYZ_INTEG02.
Note: Do not specify both the INTEGRATOR_CODE parameter and the INTEGRATOR_CODE_LIST parameter in the same command. Use only one of these parameters at a time, depending on the number of integrators you want to download.
To upload integrator definitions using the Generic Loader, specify the bneintegrator.lct configuration file, the name of the LDT file that contains the definition or definitions to upload, and - to upload all entities in the LDT file. For example:
$ FNDLOAD apps/apps 0 Y UPLOAD bneintegrator.lct bneintegrators.ldt -
Generic Loader, Oracle E-Business Suite System Administrator's Guide - Configuration
Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved.