When deploying an Oracle I/PM solutions, you must define applications, searches, inputs, and connections. Applications are the core of Oracle I/PM. An application is a type of management container for documents, defining a metadata set, storage information, and security for all documents within it. Searches enable a user to quickly retrieve a document they need, and an input definition is used to map information from an input file to the metadata fields defined in an application. Applications, searches, inputs, and connections are defined using the Oracle I/PM user interface.
You can reuse the application, search, and input definitions by exporting the desired definition to an XML file format. You can then import that definition file into other systems to make those same items available there. For example, if you created an Invoices application for Accounts Receivable and now want to create a similar application for Accounts Payable, you can start with the imported application definition and then modify it as necessary in the Oracle I/PM user interface.
Note that when exporting an application, you can explicitly export it by selecting the application and following the procedure detailed in "Exporting Definitions". However, you can also implicitly export application definitions by selecting a search or input that references the application and following the export procedure. Explicitly exported application definitions can modify existing application definitions if you specify them to do so. Implicitly exported application definitions cannot modify existing definitions.
To export a definition file, do the following:
Under Tools in the navigator pane, select Export Definitions. The Export Definitions: Export Comments Page page displays.
Enter any comments about the exported definitions, such as the need for exporting, and click Next. The Export Definitions: Applications Page is displayed.
Enable any application definitions needed for export.
Click Next. The Export Definitions: Searches Page is displayed.
Enable any search definitions needed for export.
Click Next. The Export Definitions: Inputs Page.
Enable any input definitions needed for export.
Click Next. The Export Definitions: Summary Page is displayed.
Review the information on the summary page and ensure it is accurate. Use the navigation train to go back and make any changes. When satisfied, click Create Export File.
After you have created an definition file, complete the following steps to import it:
Under Tools in the navigator pane, click Import Definitions. The Import Definitions: File Location Page displays.
Enter the path or click Browse to navigate to the definition file that contains the exported definitions you want to import. Add any necessary comments, and click Next. The Import Definitions: Select Imports Page displays.
Note:If using your keyboard rather than your mouse to select the Browse button, use the Space bar to execute the Browse button function and open the dialog box. The Enter key does not execute the Browse button function.
Select the action for each application, input and search definition to be imported. Options are:
Overwrite: the imported definition overwrites the current definition
Add: the imported definition is added to the system
Note:Remember that implicitly exported application definitions cannot overwrite existing definitions. Implicitly exported application definitions are those applications that were not explicitly selected for export, but are referenced by a search or input definition that was selected.
If more than one repository is available, select the repository to be used with the imported definition. Click Next. The Import Definitions: Validate Imports Page displays.
Select your decisions about whether to change the Security, Document Security, Storage Policy, and BPEL settings of the imported definitions. Click Submit. The Import Summary page displays.