13 Updating Order-to-Activate Cartridges

Importing the Installation Cartridge for Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x

To import the installation cartridge for Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x:

1. Ensure that you have the following software installed on your Windows system:

   • The supported version of WebLogic Server and ADF. See "Software Requirements" for more information.

   • OSM Administrator Software Development Kit (SDK) components

   • Java JDK: Use the version of Java that matches the one being used by the OSM server. See "Software Requirements" for more information.

   • Eclipse with Design Studio plug-ins

   Note:

   The Order-to-Activate cartridges require the following Design Studio plug-ins:

   • Design Studio Platform

   • Design Studio for Order and Service Management

   • Design Studio for Order and Service Management Orchestration

   • Design Studio for Order and Service Management Integration

   • Design Studio for Order and Service Management Orchestration Application Integration Architecture (AIA)

   See Design Studio Installation Guide for information about installing Design Studio plug-ins and how to confirm which plug-ins are installed.

2. If you do not already have it available, locate or download the appropriate version of the unmodified cartridges.

   • You should always ensure that you use the latest patch of the cartridges, if one is available. See "Getting the Latest Patch for Your Version of the Cartridges" for more information.

   • If you are downloading the latest version from the Oracle software delivery website, select Oracle Communications Order and Service Management Cartridge for Provisioning Fulfillment and select your platform.

   • If you have already downloaded the Order-to-Activate cartridges, locate the OracleComms_OSM_O2A_CartridgesInstaller_byyyymmdd.zip file.

3. Unzip the OracleComms_OSM_O2A_CartridgesInstaller_byyyymmdd.zip file.

   The OSM.PIP directory containing the OracleComms_OSM_O2A_Install.zip file is created.

4. Verify that Design Studio is running.

5. From the File menu, select Import Studio Project.

   The Import Projects dialog box is displayed.

6. Select Select archive file and click Browse.

7. Browse to the OSM.PIP directory and select OracleComms_OSM_O2A_Install.zip.

8. Click Open.

   The OracleComms_OSM_O2A_Install project is displayed and selected in the Projects field.

9. Click Finish.

   The OracleComms_OSM_O2A_Install project is imported.

Importing Unmodified OSM Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x Cartridges

If you are updating unmodified Order-to-Activate cartridges, follow this procedure.

To import the OSM Order-to-Activate cartridges:

1. Open the Ant view.

2. Right-click in the Ant view and select Add Buildfiles.

   The Buildfile Selection dialog box is displayed.

3. Expand OracleComms_OSM_O2A_Install and select OSM.O2A.Installation.xml.

4. Click OK.

   The OSM.O2A.Installation item is displayed in the Ant view.

5. Right-click OSM.O2A.Installation and select Run As.

6. Select Ant Build... (not Ant Build), as shown in Figure 13-1.

   Figure 13-1 Run As Menu

   
   

   The Edit Configuration dialog box is displayed.

7. Click the Build tab and deselect Build before launch.

8. Click the Properties tab and deselect Use global properties as specified in the Ant runtime preferences.

9. Click the JRE tab and select Run in the same JRE as the Workspace.

10. Click Close and click Yes.

11. In the Ant view, expand OSM.O2A.Installation and double-click import_solution.

12. In the first Ant Input Request window, do one of the following:

    • To import cartridges for the Complex solution topology, enter c and click OK.

    • To import the cartridges for the Typical solution topology, enter t and click OK.

    • To import the cartridges for the Simple solution topology, enter s and click OK.

13. In the second Ant Input Request window, do one of the following:

    • To deploy both central order management and service order management to the same OSM instance, enter s and click OK.

    • To deploy central order management and service order management to different OSM instances, enter m and click OK.

    The cartridges appropriate for the settings you selected are imported into the workspace. This may take a few minutes.

Importing Modified Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x Cartridges

If you are updating modified Order-to-Activate cartridges, follow this procedure.

To import the modified OSM Order-to-Activate cartridges:

1. Import the latest patch of the Order-to-Activate cartridges for your version into your Design Studio workspace for OSM 7.3.5.

   For example, if you have been working with Order-to-Activate version 7.2.0.6, import the cartridges for the latest patch of 7.2.0 (for example, 7.2.0.10).

   For more information about how to do this see "Importing Unmodified OSM Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x Cartridges."

2. Import any custom cartridges that you created into the workspace.

3. If you have modified any sample Order-to-Activate cartridges (which are unsealed), such as composite cartridges, check the README file for the latest patch, which tells you what cartridges have been changed by the patch. Then do one of the following:

   • If the cartridges you modified have not been updated by the patch, import your modified versions of the cartridges.

   • If the cartridges you modified have been updated by the patch, you must re-create your modifications in the versions of the cartridges from the latest patch.

4. In general, you should not unseal and modify cartridges that are sealed. If you have done this, check the README file for the latest patch, which tells you what cartridges have been changed by the patch. Then do one of the following:

   • If the cartridges you modified have not been updated by the patch, import your modified versions of the cartridges.

   • If the cartridges you modified have been updated by the patch, you must re-create your modifications in the versions of the cartridges from the latest patch.

Migrating the Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x Cartridges

To migrate the modified or unmodified Order-to-Activate 7.2, 2.0.1.x, or 2.1.0.x cartridges:

1. Right-click in the Ant view and select Add Buildfiles.

   The Buildfile Selection dialog box is displayed.

2. Expand the OSM.O2A.Cartridges.Migration cartridge and expand the 7.2.0, 2.0.1.3, 2.0.1.4, 2.1.0.1, or 2.1.0.2 directory, depending on your version of the cartridges. Click the migration.xml file and click OK.

   The appropriate file, OSM.O2A.Cartridges.7.2.0_to_7.3.5_Migration, OSM.O2A.Cartridges.2.0.1.3_to_7.3.5_Migration, OSM.O2A.Cartridges.2.0.1.4_to_7.3.5_Migration, OSM.O2A.Cartridges.2.1.0.1_to_7.3.5_Migration, or OSM.O2A.Cartridges.2.1.0.2_to_7.3.5_Migration is displayed in the Ant view.

3. Configure the buildfile for the file you have added:

   1. In the Ant view, right-click the name of the file and select Run As.

   2. Select Ant Build... (not Ant Build), as shown in Figure 13-1.

      The Edit Configuration dialog box is displayed.

   3. Click the Build tab and deselect Build before launch.

   4. Click the Properties tab and deselect Use global properties as specified in the Ant runtime preferences.

   5. Click the JRE tab and select Run in the same JRE as the Workspace.

   6. Click Close and click Yes.

4. In the Ant View, expand the file you added (OSM.O2A.Cartridges.7.2.0_to_7.3.5_Migration, OSM.O2A.Cartridges.2.0.1.3_to_7.3.5_Migration, OSM.O2A.Cartridges.2.0.1.4_to_7.3.5_Migration, OSM.O2A.Cartridges.2.1.0.1_to_7.3.5_Migration, or OSM.O2A.Cartridges.2.1.0.2_to_7.3.5_Migration) and double-click migrate.

5. Exit and restart Eclipse.

   If prompted to save any entities, select Yes.

   When Eclipse is restarted, the Studio Project Upgrade window is displayed, with a list of cartridges that should be upgraded.

6. Click Finish.

   The cartridges will be updated, including changing the data structures in the data dictionary. This can take several minutes. When the upgrade is finished, you are presented with the option to view the upgrade logs.

7. Exit and restart Eclipse.

   If prompted to save any entities, select Yes.

8. Build all of the cartridges.

   See the Design Studio Help for information about how to build cartridges. Some cartridge builds will fail with the following error listed in the Problems pane:

   Naming Conflict - Entity names must be unique (case-insensitively) amongst other entities of the same or similar types within a workspace.  The conflicts are: /OracleComms_Model_Base/model/Activation.applicationRole.
   

9. To solve the problem listed above, do the following:

   1. Open the Package Explorer view.

   2. Navigate to the OracleComms_Model_BaseCatalog/model directory.

   3. Remove all files in this directory that have the .applicationRole extension.

10. Clean and build all of the cartridges.

11. Configure the WebLogic Server resources for your environment.

    See "Configuring WebLogic Server Resources for Order-to-Activate 7.2" for more information.

Configuring WebLogic Server Resources for Order-to-Activate 2.0.1.x or 2.1.0.x

The process in this section configures the metadata for the composite cartridges in addition to configuring the WebLogic Server resources.

To configure the WebLogic Server resources for Order-to-activate 2.0.1.x or 2.1.0.x see OSM Cartridge Guide for Oracle Application Integration Architecture for the version of the cartridges you are updating. In the chapter titled "Performing an Interactive Installation of the Order-to-Activate Components" (version 2.1.0 or later) or "Installing the Order-to-Activate Components" (version 2.0.1), and perform the procedure in the "Configuring WebLogic Server Resources" section.

This documentation is available from the Oracle Help Center website:

http://docs.oracle.com

Configuring WebLogic Server Resources for Order-to-Activate 7.2

The process in this section configures the metadata for the composite cartridges in addition to configuring the WebLogic Server resources.

To configure the WebLogic Server resources for Order-to-Activate 7.2:

1. Open the Ant view.

2. Find the one row in Table 13-1 that matches your situation. For each cartridge listed in the corresponding "SolutionConfig.xml Files to Add" column of the table:

   1. Right-click in the Ant view and select Add Buildfiles.

      The Buildfile Selection dialog box is displayed.

   2. Expand the cartridge listed in the table and click on the SolutionConfig.xml file.

   3. Click OK.

   Table 13-1 SolutionConfig.xml Files to Use in Different Situations

   Topology	Configuration	SolutionConfig.xml Files to Add
   Simple	Central order management and service order management are on the same OSM instance	OracleComms_OSM_O2A_COMSOM_SimpleSolution
   Simple	Central order management and service order management are on different OSM instances	OracleComms_OSM_O2A_COM_SimpleSolution OracleComms_OSM_O2A_SOM_Solution
   Typical	Central order management and service order management are on the same OSM instance	OracleComms_OSM_O2A_COMSOM_TypicalSolution
   Typical	Central order management and service order management are on different OSM instances	OracleComms_OSM_O2A_COM_TypicalSolution OracleComms_OSM_O2A_SOM_Solution

   
   

   The items are displayed in the Ant view. Each SolutionConfig.xml file is listed as the name of the cartridge it was added from. For example, if you added the SolutionConfig.xml file from OracleComms_OSM_O2A_COMSOM_SimpleSolution, it is listed as OracleComms_OSM_O2A_COMSOM_SimpleSolution in the Ant view.

3. For each SolutionConfig.xml file you have added, configure the buildfile:

   1. In the Ant view, right-click the name of the cartridge for the SolutionConfig.xml file and select Run As.

   2. Select Ant Build... (not Ant Build).

      The Edit Configuration dialog box is displayed.

   3. Click the Build tab and deselect Build before launch.

   4. Click the Properties tab and deselect Use global properties as specified in the Ant runtime preferences.

   5. Click the JRE tab and select Run in the same JRE as the Workspace.

   6. Click Close and click Yes.

   7. Right-click the name of the cartridge for the SolutionConfig.xml file and select Run As again.

   8. Select Ant Build... (not Ant Build).

      The Edit Configuration dialog box is displayed.

      Note:

      It is necessary to close and reopen the Edit Configuration dialog box because after you have deselected the Use global properties... check box, Eclipse prevents you from changing any of these properties until you close and re-open the Edit Configuration dialog box.

   9. Click the Properties tab and set the appropriate values according to Table 13-2.

      Table 13-2 Values for Ant Edit Configuration Properties Tab

      Property Name	Description	Notes
      aia.emulator.serverName	Name of the cluster or server within WebLogic Server to which you want to deploy the emulators. Set this to one of the following: If OSM is installed to a cluster, set this value to the name of the cluster. If OSM is installed to the administration server, set this to the name of the administration server. If OSM is installed to a single managed server, set this value to the managed server name. If both central order management and service order management are in the same OSM server instance, set this to the name of the cluster or server for the single OSM instance. If central order management and service order management are in different OSM server instances, set this to the name of the cluster or server for central order management in the central order management buildfile and to the name of the cluster or server for service order management in the service order management buildfile.	Set this property in all files if you are installing the Oracle AIA emulators.
      cf.adminServerListenAddress	Host name of the system where the WebLogic Server for central order management is running. If you are in a clustered environment, set this to the server where the Administration server is located.	Set this if the name of the cartridge associated with the buildfile contains COM or COMSOM.
      cf.adminServerListenPort	Port on which the WebLogic Server for central order management is listening. If you are in a clustered environment, set this to the port on which the Administration server is listening.	Set this if the name of the cartridge associated with the buildfile contains COM or COMSOM.
      cf.clusterName	Name of the cluster for central order management, exactly as it is shown in the WebLogic Server console.	Set this if the name of the cartridge associated with the buildfile contains COM or COMSOM and you are in a clustered WebLogic environment.
      cf.userName	Name of a user with administrative privileges on the WebLogic Server for listening on cf.adminServerListenAddress and cf.adminServerListenPort.	Set this if the name of the cartridge associated with the buildfile contains COM or COMSOM.
      lf.adminServerListenAddress	Host name of the system where the WebLogic Server for service order management is running. If you are in a clustered environment, set this to the server where the Administration server is located.	Set this if the name of the cartridge associated with the buildfile contains SOM.
      lf.adminServerListenPort	Port on which the WebLogic Server for service order management is listening. If you are in a clustered environment, set this to the port on which the Administration server is listening.	Set this if the name of the cartridge associated with the buildfile contains SOM.
      lf.clusterName	Name of the cluster for service order management, exactly as it is shown in the WebLogic Server console.	Set this if the name of the cartridge associated with the buildfile contains SOM and you are in a clustered WebLogic environment.
      lf.userName	Name of a user with administrative privileges on the WebLogic Server listening on lf.adminServerListenAddress and lf.adminServerListenPort.	Set this if the name of the cartridge associated with the buildfile contains SOM.

      
      

   10. Click Close and click Yes.

4. For each SolutionConfig.xml file you have added, do the following:

   1. In the Ant view, expand the cartridge name and double-click config_All.

   2. The first Ant Input Request window requests the WebLogic administrator user password. Enter the password for the user you entered in cf.userName or lf.userName (whichever value you configured for the buildfile you are running). Click OK.

   3. In the second Ant Input Request window, enter y to use the same password for all of the users being created or enter n to use a different password for each user. Click OK.

   4. Enter the passwords requested for the Order-to-Activate users by the Ant Input Request windows:

      Note:

      Ensure that the passwords you enter meet the security requirements of your WebLogic Server domain. By default, the WebLogic server requires passwords of at least eight characters, with at least one numeric or special character. However, the requirements for your domain may be different.

      If you entered y in the previous step, enter the common password for the Order-to-Activate users and click OK.

      If you entered n in the previous step and the name of the cartridge associated with the buildfile contains COM, you are prompted for passwords for the following users: COM user (osm), COM Order Event user (osmoe), COM Data Change Event user (osmde), and COM Fallout user (osmfallout). Click OK after each entry.

      If you entered n in the previous step and the name of the cartridge associated with the buildfile contains SOM, you are prompted for passwords for the following users: SOM user (osmlf), SOM Order Event user (osmoelf), and SOM Order Abort user (osmlfaop). Click OK after each entry.

      If you entered n in the previous step and the name of the cartridge associated with the buildfile contains COMSOM, you are prompted for passwords for the following users: COM user (osm), COM Order Event user (osmoe), COM Data Change Event user (osmde), COM Fallout user (osmfallout), SOM user (osmlf), SOM Order Event user (osmoelf), and SOM Order Abort user (osmlfaop). Click OK after each entry.

      After you have entered the passwords and clicked OK, the system creates the users in the WebLogic domain. This may take a few minutes.

      Note:

      Although config_All has now created users in the WebLogic Server domain, it is still possible to cancel the script at a later point and rerun it. If config_All finds the users already present in the domain, it will skip adding them again and continue with the rest of the configuration process.

   5. In the next Ant Input Request window, enter s if you are using a standalone WebLogic Server environment or enter c if you are using a clustered environment. Click OK.

   6. In the next Ant Input Request window, enter d (for development environment) if you do not intend to connect to Oracle AIA or enter p (for production environment) if you intend to connect to Oracle AIA. Click OK.

      If you selected d, the queues for a development environment will be created. This may take several minutes. If you selected p, the queues will be created after the next step.

   7. Do one of the following:

      If you selected to have a development environment, in the next Ant Input Request window, enter d to deploy the Oracle AIA emulators or enter n to skip deploying the Oracle AIA emulators.

      If you selected to have a production environment, in the next Ant Input Request window, enter s and click OK. This will install a Store-and-Forward (SAF) service for communications with Oracle AIA. Do not choose b in this window, because it is not supported.

   8. If you selected to have a production environment, entered s to install a SAF service, and the name of the cartridge associated with the buildfile contains COMSOM or COM:

      Enter the Oracle AIA server user name that OSM central order management should use to connect to Oracle AIA in the next window, and click OK.

      Then, enter the password for that user in the next window, and click OK.

      Then, enter the host name and port (in the format hostname:port) that central order management should use for connecting to Oracle AIA in the next window. If the Oracle AIA server is on a WebLogic Cluster, enter all the host names and ports, separated by commas, for example:

      yourhost1.com:8001,yourhost1.com:8002,yourhost2.com:7030
      

      Click OK.

      Finally, if OSM is not deployed in a clustered WebLogic Server environment, enter the name of the WebLogic server where central order management is running, and click OK.

   9. If you selected to have a production environment, entered s to install a SAF service, and the name of the cartridge associated with the buildfile contains SOM:

      Enter the Oracle AIA server user name that OSM service order management should use to connect to Oracle AIA in the next window, and click OK.

      Then, enter the password for that user in the next window, and click OK.

      Then, enter the host name and port (in the format hostname:port) that service order management should use for connecting to Oracle AIA in the next window. If the Oracle AIA server is on a WebLogic Cluster, enter all the host names and ports, separated by commas, for example:

      yourhost1.com:8001,yourhost1.com:8002,yourhost2.com:7030
      

      Click OK.

      Finally, if OSM is not deployed in a clustered WebLogic Server environment, enter the name of the WebLogic server where service order management is running, and click OK.

   10. Click OK. The system configures the rest of the WebLogic resources. This may take a few minutes.

5. When the installer is finished, shut down any affected WebLogic domains and restart them.

6. Exit and restart Eclipse.