Importing Existing OSM Models
You can import a single order type into a cartridge project, or multiple order types into a cartridge project. After importing multiple order types into a cartridge project, you can deploy all or a specified number of the order types to an OSM run-time environment within the context of a single project.
Note:
Cartridge dependencies must exist in the workspace before importing a cartridge project. For example, when importing an OSM project that has a dependency on a Data Dictionary project, you must import the Data Dictionary project first to avoid problem markers during the project build.
For example, if you have defined a project with metadata to support the DSL services Add, Delete, and Modify for orders that come from two different sources (Siebel and Oracle Communications Billing and Revenue Management, for example), you can deploy the entire configuration to a run-time environment with a single deployment.
To import an OSM model into Design Studio:
-
From the Studio menu, select Show Design Perspective.
-
Right-click in the Solution view or Studio Projects view and select Import, then select Import Order and Service Management Model.
The Import Order and Service Management wizard is displayed.
-
Click Browse.
An import dialog box opens.
-
Select the file to import.
-
Click OK.
Design Studio returns you to the Import Order and Service Management dialog box.
-
Click Next.
-
Select the cartridge to import from the Source Cartridge list.
If multiple cartridges exist in the XML model, you must select which cartridge to import.
-
In the Target Name field, edit the default project name.
The project name must be unique among project entity types. Two projects cannot share the same name, even if they are different versions.
-
In the Target Data Dictionary field, select the dictionary to which the data elements will be added.
You can add the new data elements to a Data Dictionary that is common to all cartridges, or to a data dictionary defined for a specific cartridge. To create a new dictionary, enter the name of a new data dictionary in the Target Data Dictionary.
-
Click Next.
-
Select the orders to import.
Select orders in the Available column and use the arrow buttons to move them to the Selected column.
-
Click Next.
-
Add one or multiple automation maps to the cartridge.
Click Add to navigate to and select one or multiple automation maps. Click Remove to delete an automation map from the table.
When you configure automation plug-ins in Design Studio, the system automatically generates an automation map. However, if you are importing cartridges that contain custom automation plug-ins, you can include in the import the automation maps that define the configuration for the custom plug-ins. For each plug-in, the automation map defines whether the plug-in is associated with a task, notification, or data change event, the class name of the plug-in, and whether the plug-in receives information from OSM or from an external system.
Design Studio imports external receivers as a list of XML files into the customAutomation folder, each containing one external receiver XML fragment.
See "Working with Automation Plug-Ins" for more information.
-
Click Finish.
Design Studio imports the cartridge and adds the new project to the Studio Projects view.
Note:
If Design Studio detects entity name conflicts on import, it automatically renames the entity in the imported cartridge. The Import Summary report lists all entity name changes made during import. You may be required to edit references to the affected entity names in Java code or XSLT files. See "About Import Summary Reports" for more information.