Skip Headers
Oracle® Communications Order and Service Management Installation Guide
Release 7.2.2

E35412-06
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Updating Order-to-Activate Cartridges

The Order-to-Activate cartridges are pre-built Oracle Communications Order and Service Management (OSM) cartridges that support the Oracle Order-to-Activate business process to be used with the Oracle Communications Order to Cash Integration Pack for Oracle Communications Order and Service Management (Order to Cash Integration Pack for OSM). For more information about this product, see Cartridge Guide for Oracle Application Integration Architecture.

This chapter describes how to update earlier versions of OSM Order-to-Activate cartridges to run on OSM 7.2.2. It also contains information on how to configure Oracle WebLogic Server resources for the cartridges in your new WebLogic Server domain for OSM 7.2.2, and how to deploy the updated cartridges.

To install the Order-to-Activate 7.2 cartridges for use with OSM 7.2, see Cartridge Guide for Oracle Application Integration Architecture.

System Requirements

Before updating the Order-to-Activate cartridges, ensure the following:

  • OSM is upgraded to 7.2.2.

  • Oracle Communications Design Studio is upgraded to version 7.2.2 and your workspace is configured according to the instructions for Design Studio 7.2.2.

    The instructions in this chapter assume you are using a new (empty) OSM 7.2.2 Design Studio workspace.

  • The Oracle WebLogic Server domain for OSM 7.2.2 is running.

  • Existing user-created domain configurations, such as JMS queues, users, groups, and emulators are the same as before the OSM upgrade. (Do not re-create the system-generated users: osm, osmoe, osmde, osmfallout, osmlf, osmoelf, and osmlfaop.)

Preparing to Update the Order-to-Activate 7.0.2, 7.0.3, 7.2, and 2.0.1 Cartridges

Before updating Order-to-Activate cartridges, do the following:

Ensuring Order-to-Activate Cartridge Compatibility

To install or upgrade the Order-to-Activate cartridges, you must ensure compatibility between the following:

  • OSM software version and Order-to-Activate cartridge version

    OSM is compatible with all cartridges developed in a previous release, including Order-to-Activate cartridges. So, any OSM version is compatible with the same version or an earlier version of the Order-to-Activate cartridges.

  • OSM Order-to-Activate cartridge version and Oracle Application Integration Architecture (AIA) Order to Cash Integration Pack for OSM version

For details on Order-to-Activate cartridge compatibility, see knowledge article 1388662.1, OSM - Order to Activate O2A - AIA Compatibility Matrix on the Oracle Support Web site:

https://support.oracle.com

Note:

If you want to use Order-to-Activate 7.2.0.x cartridges with OSM 7.2.2, you must ensure that your Order-to-Activate cartridges have been upgraded to the 7.2.0.2 patch or higher.

Getting the Latest Patch for Your Version of the Cartridges

It is important to get the latest patch for the version of the cartridge you are updating. For the 7.0.2, 7.0.3, and 7.2 versions of the cartridges, the latest patch will be found on My Oracle Support inside the latest OSM patch for the appropriate version. For the 2.0.1 and later versions of the cartridges, the latest patch will be found on My Oracle Support as a separate release for AIA cartridges under the OSM product. Patches contain a complete installation of the cartridges and do not require an existing installation to be present.

Setting Design Studio Preferences

To set Design Studio preferences:

  1. Verify that Design Studio is running.

  2. From the Window menu, select Preferences.

    The Preferences dialog box is displayed.

  3. In the Preferences navigation tree, expand Oracle Design Studio.

  4. Select Order and Service Management Preferences.

    The Order and Service Management Preferences page includes the Deploy Properties pane in which you can provide home directories for various tools.

  5. In the WebLogic Home field, enter or browse to the directory in which the WebLogic Server is installed, for example, C:\Program Files\Oracle Middleware\wlserver_10.3.

  6. In the Java SDK Home field, enter or browse to the directory in which you have installed the JDK for the version of Java that matches the version of Java on your OSM server, for example, C:\Program Files\WebLogic\jdk160_33.

  7. In the OSM SDK Home field, enter or browse to the directory in which you have installed the OSM SDK, for example, C:\Program Files\Oracle Communications\OSM7\SDK.

  8. Select Inherit significance from order contributors and Inherit keys from order contributors.

  9. Expand Order and Service Management Preferences and select Application Integration Architecture (AIA) Preferences.

  10. In the Oracle Middleware Home field, enter the directory in which you have installed Oracle Middleware products, for example, C:\Program Files\WebLogic.

  11. In the Preferences navigation tree, expand Java and select Compiler. Ensure that Compiler compliance level is set to 1.6.

  12. Under Java, select Installed JREs.

  13. If the Java directory that you entered for Java SDK Home in step 6 is not displayed, add it and ensure that it is selected, as shown in Figure 12-1.

    Figure 12-1 Extract from Installed JREs Window

    Screen capture for Installed JREs section in Preferences window.
  14. Click OK.

  15. From the Project menu, deselect Build Automatically.

Downloading the Migration Package

The Migration package is now included with the OSM 7.2.2 software download, and does not need to be downloaded separately. Your existing OSM software download should include the following file:

OracleComms_OSM_O2A_CartridgesMigration_byyyymmdd.zip

This is the migration package.

Importing the Migration Package Cartridge

To import the migration package cartridge:

  1. Verify that Design Studio is running.

  2. From the Studio menu, select Show Design Perspective.

  3. From the Window menu, select Show View, and then select Package Explorer.

  4. From the Window menu, select Show View, and then select Other.

    The Show View window is displayed.

  5. Expand Ant and click Ant from below it. Click OK.

    The Ant view opens.

  6. Right click in the Package Explorer view and select Import.

    The Import dialog box is displayed.

  7. Expand the General folder and click Existing Projects into Workspace.

  8. Click Next.

    The Import Projects dialog box is displayed.

  9. Select Select archive file and click Browse.

  10. Browse to temp_install_dir and select OracleComms_OSM_O2A_CartridgesMigration_byyyymmdd.zip.

  11. Click Open.

    OSM.O2A.Cartridges.Migration is displayed and selected in the Projects field.

  12. Click Finish.

    The OSM.O2A.Cartridges.Migration project is imported.

The OSM.O2A.Cartridges.Migration project contains the following directories:

  • 7.0.2: This directory contains the resources required for migrating Order-to-Activate 7.0.2 cartridges to run on OSM 7.2.2.

  • 7.0.3: This directory contains the resources required for migrating Order-to-Activate 7.0.3 cartridges to run on OSM 7.2.2.

  • 7.2.0: This directory contains the resources required for migrating Order-to-Activate 7.2 cartridges to run on OSM 7.2.2.

  • 2.0.1: This directory contains the resources required for migrating Order-to-Activate 2.0.1 cartridges to run on OSM 7.2.2.

  • config: This directory contains configuration scripts to create users and JMS resources and scripts to build the AIA emulators and deploy them to the OSM 7.2.2 server. The scripts in this directory are used for all 7.0.x migrations. Migrations for 7.2.0 and 2.0.1 use the config_All targets from the SolutionConfig.xml files instead of the files in this directory.

Updating the Order-to-Activate Cartridges

There are four distinct scenarios for updating the Order-to-Activate cartridges, depending on your needs. Each scenario has its own process, outlined below.

Updating Unmodified or Modified Order-to-Activate 7.2 or 2.0.1 Cartridges to Run on OSM 7.2.2

Order-to-Activate 7.2 and 2.0.1 cartridges are native to OSM 7.2.0.

The following procedure updates Order-to-Activate 7.2 or 2.0.1 cartridges so that they can run on OSM 7.2.2. Use this procedure both to update the standard, unmodified Order-to-Activate 7.2 or 2.0.1 cartridges and to update a solution that is based on modified versions of the Order-to-Activate 7.2 or 2.0.1 cartridges. This procedure makes no functional changes to the contents of the cartridges.

Importing the Installation Cartridge for Order-to-Activate 7.2 or 2.0.1

To import the installation cartridge for Order-to-Activate 7.2 or 2.0.1:

  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 1.6.0: 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 make sure 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 Web site, select Oracle Communications Applications as the product pack, and access the Oracle Communications Order and Service Management Cartridges for Oracle Application Integration Architecture Media Pack item.

    • 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. In the Package Explorer view, right-click and select Import.

    The Import dialog box is displayed.

  6. Expand the General folder and select Existing Projects into Workspace.

  7. Click Next.

    The Import Projects dialog box is displayed.

  8. Select Select archive file and click Browse.

  9. Browse to the OSM.PIP folder and select OracleComms_OSM_O2A_Install.zip.

  10. Click Open.

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

  11. Click Finish.

    The OracleCgbuOsmAIAInstall project is imported.

Importing Unmodified OSM Order-to-Activate 7.2 or 2.0.1 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 12-2.

    Figure 12-2 Run As Menu

    Screen capture for selecting Ant Build... from the 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 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 or 2.0.1 Cartridges

If you are updating modified Order-to-Activate 7.2 or 2.0.1 cartridges, manually import all of the cartridges (including unmodified Oracle-supplied cartridges, modified Oracle-supplied cartridges, and any custom cartridges that you have created to work with them) from your Order-to-Activate 7.2-based or 2.0.1-based solution into your Design Studio workspace for OSM 7.2.2.

Migrating the Order-to-Activate 7.2 or 2.0.1 Cartridges

To migrate the modified or unmodified Order-to-Activate 7.2 or 2.0.1 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 or 2.0.1 directory, depending on your version of the cartridges. Click the migration.xml file and click OK.

    The appropriate file, either OSM.O2A.Cartridges.7.2.0_to_7.2.2_Migration or OSM.O2A.Cartridges.2.0.1_to_7.2.2_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).

      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 (either OSM.O2A.Cartridges.7.2.0_to_7.2.2_Migration or OSM.O2A.Cartridges.2.0.1_to_7.2.2_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. This can take several minutes. When the upgrade is finished, you are presented with the option to view the upgrade logs.

  7. Build all of the cartridges.

    See the Design Studio Help for information about how to build cartridges.

  8. Configure the WebLogic Server resources for your environment.

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

Configuring WebLogic Server Resources for Order-to-Activate 7.2 or 2.0.1

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:

  1. Open the Ant view.

  2. Find the one row in Table 12-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 12-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 12-2.

      Table 12-2 Values for Ant Edit Configuration Properties Tab

      Property Name Description Notes

      aia.emulator.serverName

      Name of the server within WebLogic Server to which you want to deploy the emulators. Set this to the name of the cluster if OSM is installed to a cluster or to the (administration or managed) server name if OSM is installed on a single server.

      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 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 AIA or enter p (for production environment) if you intend to connect to 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 AIA emulators or enter n to skip deploying the 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 AIA. Do not choose b in this window for Order-to-Activate 7.2 or 2.0.1 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 AIA server user name that OSM central order management should use to connect to 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 AIA in the next window. If the 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 AIA server user name that OSM service order management should use to connect to 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 AIA in the next window. If the 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.

Note:

If you have made a mistake setting the Design Studio preferences and it causes this procedure to fail, this will be displayed in the Console view in Design Studio. First, correct the preferences using the instructions in "Setting Design Studio Preferences." Next, go to the Properties tab of the Edit Configuration dialog box, select Use global properties as specified in the Ant runtime preferences to update the values, and then deselect Use global properties as specified in the Ant runtime preferences again. Then, select Clean from the Project menu and clean and build the OracleComms_OSM_O2A_Install project. Exit and restart Design Studio, and then begin the procedure for configuring the WebLogic Server resources again.

Updating Unmodified Order-to-Activate 7.0.2 and 7.0.3 Cartridges to Run on OSM 7.2.2

This section provides instructions for updating the unmodified Order-to-Activate 7.0.2 and 7.0.3 cartridges to run on OSM 7.2.2. You cannot use this procedure if there are pending orders for the cartridges on your OSM server, because the version number format changed between OSM 7.0.3 and OSM 7.2.2.

To update your unmodified Order-to-Activate cartridges to run on OSM 7.2.2:

  1. Get the latest patch of the appropriate version of the cartridges. See "Getting the Latest Patch for Your Version of the Cartridges" for more information about getting the correct version.

  2. Unzip the patch file.

  3. Unzip the OSM.PIP_Installer_byyyymmdd.zip file.

    The OSM.PIP directory is created containing the OracleCgbuOsmAIAInstallation.zip and OracleCgbuOsmAIAPIPCartridges.zip files used later in this procedure.

  4. Verify that Design Studio is running.

  5. Import the appropriate installation cartridge for your version of the Order-to-Activate cartridges (7.0.2 or 7.0.3) into your workspace:

    1. From the File menu, select Import.

      The Import dialog box is displayed.

    2. Expand the General folder and select Existing Projects into Workspace.

    3. Click Next.

      The Import Projects dialog box is displayed.

    4. Select Select archive file and click Browse.

    5. Browse to the directory containing the OracleCgbuOsmAIAInstallation.zip file for your version of the Order-to-Activate cartridges (7.0.2 or 7.0.3).

    6. Select Copy projects into workspace.

    7. Click Finish.

  6. Import the remaining cartridges for your version of Order-to-Activate (7.0.2 or 7.0.3) for your desired topology:

    1. From the File menu, select Import.

      The Import dialog box is displayed.

    2. Expand the General folder and select Existing Projects into Workspace.

    3. Click Next.

      The Import Projects dialog box is displayed.

    4. Select Select archive file and click Browse.

    5. Browse to the directory containing the OracleCgbuOsmAIACartridges.zip file for your version of the Order-to-Activate cartridges (7.0.2 or 7.0.3).

    6. In the Projects field, ensure that only the appropriate projects are selected:

      For the Typical topology, deselect the following projects if they are present: OracleCgbuOsmAIAInstallation, DoublePlayProductSpecificationDanube, OracleCgbuDoublePlayProductSpecNileTdDcn, and SimpleSalesOrderFulfillment.

      For the Simple topology, deselect the following projects if they are present: OracleCgbuOsmAIAInstallation, DoublePlayProductSpecificationNile, OracleCgbuDoublePlayProductSpecNileTdDcn, and TypicalSalesOrderFulfillment.

    7. Select Copy projects into workspace.

    8. Click Finish.

  7. From the Studio menu, select Show Design Perspective.

  8. Set your cartridge management variables.

    For each cartridge in your workspace, click the Cartridge editor Cartridge Management Variables tab and set the following variables as needed:

    • PURGE_CARTRIDGE_BEFORE_DEPLOY: Enter true to undeploy the previous version of a cartridge before deploying the new version, or enter false to update the cartridge with the changes for the new version.

      Note:

      If your cartridge has pending or completed orders that you do not want to purge, do not undeploy the cartridge, but deploy the new version with PURGE_CARTRIDGE_BEFORE_DEPLOY set to false.
    • ENTITY_CONFLICT_ACTION_ON_DEPLOY: Enter replace to replace the old entities with the new (default); enter ignore to add the new entities and retain the old; or enter abort to stop the process if conflicts are encountered. This variable only applies if PURGE_CARTRIDGE_BEFORE_DEPLOY is set to false.

    • PURGE_ORDER_ON_UNDEPLOY: Enter true to purge all existing orders associated with the cartridge, or enter false if you do not want the system to undeploy the cartridge if it has pending orders.

      Caution:

      Undeploying a cartridge purges all existing orders for that cartridge.
    • BUILD_DEPLOY_MODE: Set this value if you wish to override the global value for a particular cartridge. Enter optimized to allow automation components to be built and run within a common oms.ear file at run time; enter legacy to build and deploy each automation plug-in in its own .ear file; or enter both to allow automation components to be built and run in either mode, according to the dispatch mode defined on the OSM server.

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

    The Buildfile Selection dialog box is displayed.

  10. Expand the OSM.O2A.Cartridges.Migration cartridge and expand the 7.0.2 or 7.0.3 directory, depending on your version of the cartridges. Click the migration.xml file and click OK.

    The appropriate file, either OSM.O2A.Cartridges.7.0.2_to_7.2.2_Migration or OSM.O2A.Cartridges.7.0.3_to_7.2.2_Migration, is displayed in the Ant view.

  11. 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).

      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.

  12. In the Ant View, expand the file you added (either OSM.O2A.Cartridges.7.0.2_to_7.2.2_Migration or OSM.O2A.Cartridges.7.0.3_to_7.2.2_Migration) and double-click migrate.

  13. 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.

  14. Click Finish.

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

  15. 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:

    Order and Service Management Cartridge Error - The automationBuild.xml file in cartridge CartridgeName is not the right version for this DS OSM plugin release. Right click on problem marker for the Quick Fix.
    

    For each cartridge that fails to build with this error:

    1. Right-click on the error in the Problems pane and select Quick Fix.

      The Quick Fix window is displayed.

    2. Click Finish and then click OK.

    3. Build the project again.

  16. Configure the WebLogic Server resources for your environment.

    See "Configuring WebLogic Server Resources for 7.0.2 and 7.0.3 Cartridge Updates" for more information.

Updating Modified Order-to-Activate 7.0.3 Cartridges to Run on OSM 7.2.2

Order-to-Activate 7.0.3 cartridges are native to OSM 7.0.3. This procedure updates the cartridges so that they can run on OSM 7.2.2. Use this procedure if you wish to update a solution that is based on modified versions of the Order-to-Activate 7.0.3 cartridges, or if you have pending orders in your OSM server. This procedure makes no functional changes to the contents of the cartridges.

Note:

At some point in the following process, the Import OSM Common Data Dictionary window will probably be displayed. Ensure that Show this dialog in the future is selected, and click Cancel.

To update your modified Order-to-Activate 7.0.3 cartridges to run on OSM 7.2.2:

  1. Verify that Design Studio is running.

  2. Import the 7.0.3 installation cartridge into your workspace:

    1. Verify that Design Studio is running.

    2. From the File menu, select Import.

      The Import dialog box is displayed.

    3. Expand the General folder and select Existing Projects into Workspace.

    4. Click Next.

      The Import Projects dialog box is displayed.

    5. Select Select archive file and click Browse.

    6. Browse to the directory containing the OracleCgbuOsmAIAInstallation cartridge for Order-to-Activate 7.0.3.

    7. Select Copy projects into workspace.

    8. Click Finish.

  3. Manually import all of the cartridges from your solution based on Order-to-Activate 7.0.3 into your Design Studio workspace, including unmodified Oracle-supplied cartridges, modified Oracle-supplied cartridges, and any custom cartridges that you have created to work with them.

  4. From the Studio menu, select Show Design Perspective.

  5. Set your cartridge management variables.

    For each cartridge in your workspace, click the Cartridge editor Cartridge Management Variables tab and set the following variables as needed:

    • PURGE_CARTRIDGE_BEFORE_DEPLOY: Enter true to undeploy the previous version of a cartridge before deploying the new version, or enter false to update the cartridge with the changes for the new version.

      Note:

      If your cartridge has pending or completed orders that you do not want to purge, do not undeploy the cartridge, but deploy the new version with PURGE_CARTRIDGE_BEFORE_DEPLOY set to false.
    • ENTITY_CONFLICT_ACTION_ON_DEPLOY: Enter replace to replace the old entities with the new (default); enter ignore to add the new entities and retain the old; or enter abort to stop the process if conflicts are encountered. This variable only applies if PURGE_CARTRIDGE_BEFORE_DEPLOY is set to false.

    • PURGE_ORDER_ON_UNDEPLOY: Enter true to purge all existing orders associated with the cartridge, or enter false if you do not want the system to undeploy the cartridge if it has pending orders.

      Caution:

      Undeploying a cartridge purges all existing orders for that cartridge.
    • BUILD_DEPLOY_MODE: Set this value if you wish to override the global value for a particular cartridge. Enter optimized to allow automation components to be built and run within a common oms.ear file at run time; enter legacy to build and deploy each automation plug-in in its own .ear file; or enter both to allow automation components to be built and run in either mode, according to the dispatch mode defined on the OSM server.

  6. Update the library names in the OSM.AIAEmulatorsBuild.xml file:

    1. Outside Design Studio, navigate to the OracleCgbuOsmAIAInstallation directory in your workspace.

    2. Open the OSM.AIAEmulatorsBuild.xml file in a text editor or an XML editor.

    3. Change all occurrences of commons-lang-2.1.jar to commons-lang3-3.1.jar and all instances of commons-collections-3.2.jar to commons-collections-3.2.1.jar. There are several instances of each value in the file.

    4. Save and close the file.

  7. Return to Design Studio and update the Java build path by doing the following for each row in Table 12-3:

    1. In the Cartridge view, right-click the cartridge listed in the Cartridge Name column and select Properties.

    2. Select Java Build Path in the left pane of the Properties window, and click the Libraries tab.

    3. Select the library in the Old Value column and click Edit.

    4. Change the value to match the value in the New Value column and click OK.

      Table 12-3 Java Build Path Updates

      Cartridge Name Old Value New Value

      BroadbandServicesProvisioning

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      CommunicationsProvisioningOrderFulfillmentPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      CommunicationsSalesOrderFulfillmentPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuCommonDataDictionaryPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-io-1.4.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-io-2.0.1.jar

      OracleCgbuCommunicationsORPFalloutPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuOsmAIAInstallation

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-collections-3.2.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-collections-3.2.1.jar

      OracleCgbuOsmAIAInstallation

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuOsmAIAInstallation

      ORACLE_MIDDLEWARE_HOME/jdeveloper/modules/oracle.jps_11.1.1/jps-api.jar

      ORACLE_MIDDLEWARE_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar

      OracleCgbuProvisioningFallout

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuSIFalloutPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      VoIPServiceProvisioning

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar


  8. Exit and restart Design Studio.

  9. If there are no pending Order-to-Activate orders in your OSM instance, change the target version and cartridge versions to be compatible with OSM 7.2.2. If there are pending Order-to-Activate orders in your OSM instance, you must skip this step. For each cartridge in your workspace:

    1. In the Cartridge editor Properties tab for the cartridge, change the value of Target Version from 7.0.3 to 7.2.0.

    2. Open the Package Explorer view.

    3. Open the CartridgeName/xmlCatalogs/core/catalog.xml file.

    4. Click the Source tab.

    5. Each rewritePrefix attribute in the file includes the string 1.0.0. Change this value to 1.0.0.0.0.

  10. In the Package Explorer view, replace the OracleCgbuCommonDataDictionaryPIP/resources/osm-pip-utility.jar file with the OSM.O2A.Cartridges.Migration/7.0.3/OracleCgbuCommonDataDictionaryPIP/resources/osm-pip-utility.jar file.

    This will replace the Order-to-Activate 7.0.3 version of the utility library with the 7.2.2 version from the migration package.

  11. Set up the event views for the orders in the solution by doing the following for each row in Table 12-4:

    1. Expand the cartridge listed in the Cartridge column in Table 12-4 and open the order editor for the order in the Order column.

    2. Click the Events tab for the order editor.

    3. In the Milestone list, select the value in the Milestone column.

    4. In the Automation list, select the value in the Automation column.

    5. Click Select and, in the resulting window, select the value in the View column.

      Table 12-4 Milestone Automation Event Notification View Updates

      Cartridge Order Milestone Automation View

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      completion

      ProvisionOrderCompleteEventHandler

      CommunicationsProvisioningOrderQueryTask

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      creation

      LFCheckCreationOrderFailureBean

      CommunicationsProvisioningOrderQueryTask

      BroadbandServicesProvisioning

      BroadbandServicesProvisioningOrder

      completion

      BroadbandServiceOrderCompleteEventHandlerBean

      BroadbandServicesProvisioningOrderQueryTask

      VoIPServiceProvisioning

      VoIPServiceProvisioningOrder

      completion

      VoIPServiceOrderCompleteEventHandlerBean

      VoIPServiceProvisioningOrderQueryTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      completion

      SalesOrderCompleteEventHandlerBean

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      stateChange

      OrderStateChangeHandler

      FalloutNotificationTask


  12. Set up the event views for the orders in the solution by doing the following for each row in Table 12-5:

    1. Expand the cartridge listed in the Cartridge column in Table 12-5 and open the order editor for the order in the Order column.

    2. Click the Notifications tab for the order editor and in the event list on the left, select the value in the Event column.

    3. Click the Automation subtab.

    4. In the Automation list, select the value in the Automation column.

    5. Click Select and, in the resulting window, select the value in the View column.

      Table 12-5 Event Notification View Updates

      Cartridge Order Event Automation View

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      SendFault2AIAEH

      SendFault2AIAEH

      CommunicationsProvisioningOrderQueryTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      CreateOrderFalloutNotification

      CreateOrderFalloutNotification

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      CloseFalloutTroubleTicket

      CloseFalloutTroubleTicket

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      NotifyCRMofOrderFalloutStatus

      NotifyCRMofOrderFalloutStatusBean

      FalloutNotificationTask


  13. Modify the InitiateBillingSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the InitiateBillingSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. In the Name field, enter InitiateBillingResponseBean.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to InitiateBillingSITask.InitiateBillingResponseBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{O2A_INBOUND_CREATE_BILLING_RESPONSE_QUEUE_JNDI}, and remove the value from the Message Property Selector field.

    9. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to AIAEBMResponse.xqy, and deselect Update Order.

  14. Modify the ProvisionOrderSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the ProvisionOrderSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. In the Name field, enter ProvisioningResponseBean.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to ProvisionOrderSITask.ProvisioningResponseBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{O2A_INBOUND_CREATE_PROV_RESPONSE_QUEUE_JNDI}, and change the value of Message Property Selector to CGBUPIPCFFALLOUT IS NULL.

    9. Click the Correlation tab in the Properties pane, select XML Body in the Correlation drop-down list, and enter the following into the XML Body field:

      (*[local-name()='ProcessFulfillmentOrderUpdateEBM']/*[local-name()='DataArea']/*[local-name()='ProcessFulfillmentOrderUpdate']/*[local-name()='Identification']/*[local-name()='BusinessComponentID']) |
      (*[local-name()='ProcessFulfillmentOrderUpdateEBM']/*[local-name()='EBMHeader']/*[local-name()='Sender']/*[local-name()='ObjectCrossReference']/*[local-name()='SenderObjectIdentification']/*[local-name()='BusinessComponentID']) |
      (*[local-name()='OrderFalloutNotification']/*[local-name()='OrderID']/*[local-name()='AlternateObjectKey']/*[local-name()='ID' and @schemeID='CFS_ORDER_KEY'])
      
    10. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to AIAEBMResponse.xqy, and deselect Update Order.

  15. Modify the SyncCustomerSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the SyncCustomerSITask task and click the Automation tab.

    3. In the list, select SyncCustomerResponseBean, and then click Properties.

    4. On the Details tab in the Properties pane, change the value for EJB Name to SyncCustomerSITask.SyncCustomerResponseBean.

  16. Modify the CommunicationsServicesProvisioningOrderSIEntryPointSITask automated task:

    1. Expand the CommunicationsProvisioningOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the CommunicationsServicesProvisioningOrderSIEntryPointSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. Enter CommunicationsServicesProvisioningOrderUpdateUndoBean in the Name field.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to CommunicationsServicesProvisioningOrderSIEntryPointSITask.CommunicationsServicesProvisioningOrderUpdateUndoBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{O2A_INTERNAL_SERVICE_PROVISIONING_UPDATE_QUEUE_JNDI}, and remove the value from the Message Property Selector field.

    9. Click the Correlation tab in the Properties pane, ensure the Correlation field is set to Message Property, and enter OMSOrderID into the Message Property field.

    10. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to CommunicationsServicesProvisioningOrderUpdate.xqy, and deselect Update Order.

  17. If you updated the target version for your cartridges to 7.2.0 in step 9 (that is, if you have no pending Order-to-Activate orders in your OSM instance), modify the CommunicationsSalesOrderLine order item specification. If you did not update the Target Version for your cartridges to 7.2.0 in step 9, you must skip this step.

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Order Item Specifications, and then expand LINE.

    2. Open the OpenCommunicationsSalesOrderLine order item specification and click the Order Item Dependencies tab.

    3. In the Order Item Dependencies list, select interOrderDependency.

    4. In the XQuery subtab on the right, there is a namespace declaration for osmc. In that declaration, the text 1.0.0 is present. Change that text to 1.0.0.0.0.

  18. 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.

  19. Click Finish to upgrade the cartridges.

    This can take several minutes. When the upgrade is finished, you are presented with the option to view the upgrade logs.

  20. 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:

    Order and Service Management Cartridge Error - The automationBuild.xml file in cartridge CartridgeName is not the right version for this DS OSM plugin release. Right click on problem marker for the Quick Fix.
    

    For each cartridge that fails to build with this error:

    1. Right-click on the error in the Problems pane and select Quick Fix.

      The Quick Fix window is displayed.

    2. Click Finish and then click OK.

    3. Rebuild the project.

  21. Configure the WebLogic Server resources for your environment.

    See "Configuring WebLogic Server Resources for 7.0.2 and 7.0.3 Cartridge Updates" for more information.

Updating Modified Order-to-Activate 7.0.2 Cartridges to Run on OSM 7.2.2

Order-to-Activate 7.0.2 cartridges are native to OSM 7.0.2. This procedure updates the cartridges so that they can run on OSM 7.2.2. Use this procedure if you wish to update a solution that is based on modified versions of the Order-to-Activate 7.0.2 cartridges, or if you have pending orders in your OSM server.This procedure makes no functional changes to the contents of the cartridges.

Note:

At some point in the following process, the Import OSM Common Data Dictionary window will probably be displayed. Do not deselect Show this dialog in the future and click Cancel.

You do not need to import the data dictionary now because you are dealing with an existing set of projects. Later, if you add new projects, you should import the data dictionary.

To update your modified Order-to-Activate 7.0.2 cartridges to run on OSM 7.2.2:

  1. Verify that Design Studio is running.

  2. Import the 7.0.2 installation cartridge into your workspace:

    1. From the File menu, select Import.

      The Import dialog box is displayed.

    2. Expand the General folder and select Existing Projects into Workspace.

    3. Click Next.

      The Import Projects dialog box is displayed.

    4. Select Select archive file and click Browse.

    5. Browse to the directory containing the OracleCgbuOsmAIAInstallation cartridge for Order-to-Activate 7.0.2.

    6. Select Copy projects into workspace.

    7. Click Finish.

  3. Manually import all of the cartridges from your solution based on Order-to-Activate 7.0.2 into your Design Studio workspace, including unmodified Oracle-supplied cartridges, modified Oracle-supplied cartridges, and any custom cartridges that you have created to work with them.

  4. From the Studio menu, select Show Design Perspective.

  5. Set your cartridge management variables.

    For each cartridge in your workspace, click the Cartridge editor Cartridge Management Variables tab and set the following variables as needed:

    • PURGE_CARTRIDGE_BEFORE_DEPLOY: Enter true to undeploy the previous version of a cartridge before deploying the new version, or enter false to update the cartridge with the changes for the new version.

      Note:

      If your cartridge has pending or completed orders that you do not want to purge, do not undeploy the cartridge, but deploy the new version with PURGE_CARTRIDGE_BEFORE_DEPLOY set to false.
    • ENTITY_CONFLICT_ACTION_ON_DEPLOY: Enter replace to replace the old entities with the new (default); enter ignore to add the new entities and retain the old; or enter abort to stop the process if conflicts are encountered. This variable only applies if PURGE_CARTRIDGE_BEFORE_DEPLOY is set to false.

    • PURGE_ORDER_ON_UNDEPLOY: Enter true to purge all existing orders associated with the cartridge, or enter false if you do not want the system to undeploy the cartridge if it has pending orders.

      Caution:

      Undeploying a cartridge purges all existing orders for that cartridge.
    • BUILD_DEPLOY_MODE: Set this value if you wish to override the global value for a particular cartridge. Enter optimized to allow automation components to be built and run within a common oms.ear file at run time; enter legacy to build and deploy each automation plug-in in its own .ear file; or enter both to allow automation components to be built and run in either mode, according to the dispatch mode defined on the OSM server.

  6. Update the library names in the OSM.AIAEmulatorsBuild.xml file:

    1. Outside Design Studio, navigate to the OracleCgbuOsmAIAInstallation directory in your workspace.

    2. Open the OSM.AIAEmulatorsBuild.xml file in a text editor or an XML editor.

    3. Change all occurrences of commons-lang-2.1.jar to commons-lang3-3.1.jar and all instances of commons-collections-3.2.jar to commons-collections-3.2.1.jar. There are several instances of each value in the file.

    4. Save and close the file.

  7. Return to Design Studio and update the Java Build Path by doing the following for each row in Table 12-6:

    1. In the Cartridge view, right-click the cartridge listed in the Cartridge Name column in Table 12-6 and select Properties.

    2. Select Java Build Path in the left pane of the Properties window, and click the Libraries tab.

    3. Find the value in the Old Value column. Select that library and click Edit.

    4. Change the value to match the value in the New Value column and click OK.

      Table 12-6 Java Build Path Updates

      Cartridge Name Old Value New Value

      BroadbandServicesProvisioning

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      CommunicationsProvisioningOrderFulfillmentPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      CommunicationsSalesOrderFulfillmentPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuCommonDataDictionaryPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-io-1.4.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-io-2.0.1.jar

      OracleCgbuCommunicationsORPFalloutPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuOsmAIAInstallation

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-collections-3.2.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-collections-3.2.1.jar

      OracleCgbuOsmAIAInstallation

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuProvisioningFallout

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      OracleCgbuSIFalloutPIP

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar

      VoIPServiceProvisioning

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang-2.1.jar

      OSM_SDK_HOME/Automation/automationdeploy_bin/commons-lang3-3.1.jar


  8. Exit and restart Design Studio.

  9. If there are pending Order-to-Activate orders in your OSM instance, change the target versions for your cartridges. For each cartridge in your workspace, in the cartridge editor Properties tab for the cartridge, change the value of Target Version from 7.0.1 to 7.0.3. If there are no pending Order-to-Activate orders in your OSM instance, skip this step and go to step 10.

  10. If there are no pending Order-to-Activate orders in your OSM instance, change the target version and cartridge versions to be compatible with OSM 7.2.2. If there are pending Order-to-Activate orders in your OSM instance, you must skip this step. For each cartridge in your workspace:

    1. In the Cartridge editor Properties tab for the cartridge, change the value of Target Version from 7.0.1 to 7.2.0.

    2. Open the Package Explorer view.

    3. Open the CartridgeName/xmlCatalogs/core/catalog.xml file.

    4. Click the Source tab.

    5. Each rewritePrefix attribute in the file includes the version 1.0.0. Change this version to 1.0.0.0.0.

  11. In the Package Explorer view, replace the Order-to-Activate 7.0.2 version of the utility library with the 7.2.2 version from the migration package by replacing the OracleCgbuCommonDataDictionaryPIP/resources/osm-pip-utility.jar file with the OSM.O2A.Cartridges.Migration/7.0.2/OracleCgbuCommonDataDictionaryPIP/resources/osm-pip-utility.jar file.

  12. Set up the event views for the orders in the solution. For each row in Table 12-7:

    1. Expand the cartridge listed in the Cartridge column in Table 12-7 and open the order editor for the order in the Order column.

    2. Click the Events tab for the order editor.

    3. In the Milestone list, select the value in the Milestone column.

    4. In the Automation list, select the value in the Automation column.

    5. Click Select and, in the resulting window, select the value in the View column.

      Table 12-7 Milestone Automation Event Notification View Updates

      Cartridge Order Milestone Automation View

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      completion

      ProvisionOrderCompleteEventHandler

      CommunicationsProvisioningOrderQueryTask

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      creation

      LFCheckCreationOrderFailureBean

      CommunicationsProvisioningOrderQueryTask

      BroadbandServicesProvisioning

      BroadbandServicesProvisioningOrder

      completion

      BroadbandServiceOrderCompleteEventHandlerBean

      BroadbandServicesProvisioningOrderQueryTask

      VoIPServiceProvisioning

      VoIPServiceProvisioningOrder

      completion

      VoIPServiceOrderCompleteEventHandlerBean

      VoIPServiceProvisioningOrderQueryTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      completion

      SalesOrderCompleteEventHandlerBean

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      stateChange

      OrderStateChangeHandler

      FalloutNotificationTask


  13. Set up the event views for the orders in the solution. For each row in Table 12-8:

    1. Expand the cartridge listed in the Cartridge column in Table 12-8 and open the order editor for the order in the Order column.

    2. Click the Notifications tab for the order editor and in the event list on the left, select the value in the Event column.

    3. Click the Automation subtab.

    4. In the automation list, select the value in the Automation column.

    5. Click Select and, in the resulting window, select the value in the View column.

      Table 12-8 Event Notification View Updates

      Cartridge Order Event Automation View

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsProvisioningOrder

      SendFault2AIAEH

      SendFault2AIAEH

      CommunicationsProvisioningOrderQueryTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      CreateOrderFalloutNotification

      CreateOrderFalloutNotification

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      CloseFalloutTroubleTicket

      CloseFalloutTroubleTicket

      FalloutNotificationTask

      CommunicationsSalesOrderFulfillmentPIP

      CommunicationsSalesOrder

      NotifyCRMofOrderFalloutStatus

      NotifyCRMofOrderFalloutStatusBean

      FalloutNotificationTask


  14. Modify the InitiateBillingSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the InitiateBillingSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. In the Name field, enter InitiateBillingResponseBean.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to InitiateBillingSITask.InitiateBillingResponseBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{WEBSERVICE_CREATE_BILLING_RESPONSE_QUEUE_JNDI}, and remove the value from the Message Property Selector field.

    9. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to AIAEBMResponse.xqy, and deselect Update Order.

  15. Modify the ProvisionOrderSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the ProvisionOrderSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. In the Name field, enter ProvisioningResponseBean.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to ProvisionOrderSITask.ProvisioningResponseBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{WEBSERVICE_CREATE_PROV_RESPONSE_QUEUE_JNDI}, and change the value of Message Property Selector to CGBUPIPCFFALLOUT IS NULL.

    9. Click the Correlation tab in the Properties pane, select XML Body in the Correlation drop-down list, and enter the following into the XML Body field:

      (*[local-name()='ProcessFulfillmentOrderUpdateEBM']/*[local-name()='DataArea']/*[local-name()='ProcessFulfillmentOrderUpdate']/*[local-name()='Identification']/*[local-name()='BusinessComponentID']) |
      (*[local-name()='ProcessFulfillmentOrderUpdateEBM']/*[local-name()='EBMHeader']/*[local-name()='Sender']/*[local-name()='ObjectCrossReference']/*[local-name()='SenderObjectIdentification']/*[local-name()='BusinessComponentID']) |
      (*[local-name()='OrderFalloutNotification']/*[local-name()='OrderID']/*[local-name()='AlternateObjectKey']/*[local-name()='ID' and @schemeID='CFS_ORDER_KEY'])
      
    10. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to AIAEBMResponse.xqy, and deselect Update Order.

  16. Modify the SyncCustomerSITask automated task:

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the SyncCustomerSITask task and click the Automation tab.

    3. In the list, select SyncCustomerResponseBean, and then click Properties.

    4. On the Details tab in the Properties pane, change the value for EJB Name to SyncCustomerSITask.SyncCustomerResponseBean.

  17. Modify the CommunicationsServicesProvisioningOrderSIEntryPointSITask automated task:

    1. Expand the CommunicationsProvisioningOrderFulfillmentPIP cartridge, expand Automated Tasks, and then expand TASK.

    2. Open the CommunicationsServicesProvisioningOrderSIEntryPointSITask task and click the Automation tab.

    3. Click Add.

      The Add Automation window is displayed.

    4. Enter CommunicationsServicesProvisioningOrderUpdateUndoBean in the Name field.

    5. Select XQuery Automator from the Automation Type drop-down list, select the External Event Receiver option, and then click OK.

    6. In the Automation list, select the automation you just created, and click Properties.

    7. On the Details tab in the Properties pane, change the value for EJB Name to CommunicationsServicesProvisioningOrderSIEntryPointSITask.CommunicationsServicesProvisioningOrderUpdateUndoBean and change the value for Run As to oms-automation.

    8. Click the External Event Receiver tab in the Properties pane, change the value of JNDI Name to %{SERVICE_PROVISIONING_UPDATE_QUEUE_JNDI}, and remove the value from the Message Property Selector field.

    9. Click the Correlation tab in the Properties pane, ensure the Correlation field is set to Message Property, and enter OMSOrderID into the Message Property field.

    10. Click the XQuery tab in the Properties pane, ensure the Bundle In option is selected, set the value for XQuery to CommunicationsServicesProvisioningOrderUpdate.xqy, and deselect Update Order.

  18. If you updated the Target Version for your cartridges to 7.2.0 in step 10 (that is, if you have no pending Order-to-Activate orders in your OSM instance), modify the CommunicationsSalesOrderLine order item specification. If you did not update the Target Version for your cartridges to 7.2.0 in step 10, you must skip this step.

    1. Expand the CommunicationsSalesOrderFulfillmentPIP cartridge, expand Order Item Specifications, and then expand LINE.

    2. Open the OpenCommunicationsSalesOrderLine order item specification and click the Order Item Dependencies tab.

    3. Select interOrderDependency in the list.

    4. In the XQuery subtab on the right, there is a namespace declaration for osmc. In that declaration, the text 1.0.0 is present. Change that text to 1.0.0.0.0.

  19. Update XQuery files to remove hard-coded passwords and optionally to change the cartridge version numbers.

    1. Outside of Design Studio, navigate to the OSM.O2A.Cartridges.Migration\7.0.2 directory in your workspace.

    2. Each of the following directories has a resources directory that contains XQuery files.

      CommunicationsProvisioningOrderFulfillmentPIP

      CommunicationsSalesOrderFulfillmentPIP

      OracleCgbuSIFalloutPIP

    3. The XQuery files in this directory have two versions each: one with the normal XQuery filename, and one with that name prefixed by before_. For each of the pairs of files, determine the difference between the normal file and the before_ file.

    4. If you updated the Target Version for your cartridges to 7.2.0 in step 10 (that is, if you have no pending Order-to-Activate orders in your OSM instance), copy all of the differences from the regular XQuery file (for example, AbortLFOrderRequest.xqy) in the OSM.O2A.Cartridges.Migration\7.0.2\CartridgeName\resources directory to the corresponding file in the corresponding directory for your corresponding 7.0.2 cartridge.

    5. If you did not update the Target Version for your cartridges to 7.2.0 in step 10 (that is, if you have pending Order-to-Activate orders in your OSM instance), copy all (except as noted below) of the differences from the regular XQuery file (for example, AbortLFOrderRequest.xqy) in the OSM.O2A.Cartridges.Migration\7.0.2\CartridgeName\resources directory to the corresponding file in the corresponding directory for your corresponding 7.0.2 cartridge.

      Do not copy the changes that relate to changing the version number of the cartridge, that is, where the line in the 7.0.2 cartridge (and in the before_ file) looks similar to this:

      declare namespace osmc="urn:oracle:names:ordermanagement:cartridge:CommunicationsSalesOrderFulfillmentPIP:1.0.0:view:CommunicationsSalesOrderQueryTask";
      

      and the line in the regular XQuery file looks similar to this:

      declare namespace osmc="urn:oracle:names:ordermanagement:cartridge:CommunicationsSalesOrderFulfillmentPIP:1.0.0.0.0:view:CommunicationsSalesOrderQueryTask";
      
  20. If your build and deploy mode is set to Internal or Both, rename the following .java files to have different file extensions so that they are not included in the build. For example, you could change LogOrderActivity.java to LogOrderActivity.java_orig.

    • In the OracleCgbuCommunicationsORPFalloutPIP cartridge:

      • src\oracle\communications\ordermanagement\log\LogOrderActivity.java

      • src\oracle\communications\ordermanagement\util\date\DateUtil.java

    • In the OracleCgbuProvisioningFallout cartridge:

      • src\oracle\communications\ordermanagement\log\LogOrderActivity.java

      • src\oracle\communications\ordermanagement\util\ThreadLocalMap.java

    For more information about build and deploy modes, see the Design Studio Modeling OSM Processes Help.

  21. If you are using the AIA emulators, do the following:

    1. Outside Design Studio, navigate to the OracleCgbuOsmAIAInstallation\resources directory in your workspace.

    2. Edit the following files in a text or XML editor:

      CF_PIPFallout2OrderNotification.xqy

      CreateSystemAdminOrderForIbMessageRecovery.xquery

      ErrorFault2OrderFaultNotificationCreateOrder.xqy

      ProvisionOrderRequest2CreateOrder.xqy

    3. In each of the files above, locate any lines containing the string PasswordText and change the value of the element to the correct password for your emulators. For example, you would change this line:

      <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">osmadmin</wsse:Password>
      

      to something that looks similar to this:

      <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">osmadmin1</wsse:Password>
      
  22. 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.

  23. Click Finish to upgrade the cartridges.

    This can take several minutes. When the upgrade is finished, you are presented with the option to view the upgrade logs.

  24. 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:

    Order and Service Management Cartridge Error - The automationBuild.xml file in cartridge CartridgeName is not the right version for this DS OSM plugin release. Right click on problem marker for the Quick Fix.
    

    For each cartridge that fails to build with this error:

    1. Right-click on the error in the Problems pane and select Quick Fix.

      The Quick Fix window is displayed.

    2. Click Finish and then click OK.

    3. Rebuild the project.

  25. Configure the WebLogic Server resources for your environment.

    See "Configuring WebLogic Server Resources for 7.0.2 and 7.0.3 Cartridge Updates" for more information.

Configuring WebLogic Server Resources for 7.0.2 and 7.0.3 Cartridge Updates

The following section provides the procedure for configuring WebLogic Server resources. It must be performed for 7.0.2 and 7.0.3 cartridge updates.

Setting Up the Configuration File for Connecting to AIA

If you are going to connect to an instance of AIA (instead of using the AIA emulators), you need to configure a file. The file you configure will depend on whether OSM is running on a WebLogic Server cluster or a WebLogic Server standalone server.

Setting Up the Configuration File for OSM on WebLogic Cluster

To set up the configuration file if OSM is running on a WebLogic Server cluster:

  1. Outside Design Studio, in the directory for your Design Studio workspace, browse to the OracleComms_OSM_O2A_Configuration/config-scripts/saf-cluster/ directory.

  2. Edit the config-cluster-saf.properties file.

  3. Change the values for the parameters in Table 12-9:

    Table 12-9 Parameters to Edit in the config-cluster-saf.properties File

    Parameter Description

    adminServerListenAddress

    Host name of the system where the WebLogic Server for central order management is running.

    adminServerListenPort

    Port on which the WebLogic Server for central order management is listening.

    adminServerName

    Name of the WebLogic server listening on adminServerListenAddress and adminServerListenPort.

    userName

    Name of a user with administrative privileges on the WebLogic server listening on adminServerListenAddress and adminServerListenPort.

    passWord

    Password of the user defined in the userName parameter.

    saf_FileStoreDir

    A directory on the system defined in the adminServerListenAddress parameter. If the value starts with a forward slash, it indicates an absolute path on the system. If the value does not begin with a forward slash, it indicates a path inside the domain directory for the server. This directory will be created if it does not exist.

    fmwRemoteServerListenAddress

    Host name of the system where the WebLogic Server for AIA is running. If AIA is running in a clustered WebLogic Server environment, enter values for all of the servers, in the format managed_server_name.hostname:port separated by commas, for example:

    firstMS.yourhost.com:8001,secondMS.yourhost.com:8002
    

    fmwRemoteServerUserName

    Name of the user that OSM should use to connect to AIA.

    fmwRemoteServerPassWord

    Password of the user defined in the fmwRemoteServerUserName parameter.


  4. Save and close the file.

Setting Up the Configuration File for OSM on Standalone WebLogic Server

To set up the configuration file if OSM is running on a WebLogic Server standalone server:

  1. Outside Design Studio, in the directory for your Design Studio workspace, browse to the OracleComms_OSM_O2A_Configuration/config-scripts/saf-standalone directory.

  2. Edit the config-standalone-saf.properties file.

  3. Change the values for the parameters in Table 12-10:

    Table 12-10 Parameters to Edit in the config-standalone-saf.properties File

    Parameter Description

    adminServerListenAddress

    Host name of the system where the WebLogic server for central order management is running.

    adminServerListenPort

    Port on which the WebLogic server for central order management is listening.

    adminServerName

    Name of the WebLogic server listening on adminServerListenAddress and adminServerListenPort.

    userName

    Name of a user with administrative privileges on the WebLogic server listening on adminServerListenAddress and adminServerListenPort.

    passWord

    Password of the user defined in the userName parameter.

    saf_FileStoreDir

    A directory on the system defined in the adminServerListenAddress parameter. If the value starts with a forward slash, it indicates an absolute path on the system. If the value does not begin with a forward slash, it indicates a path inside the domain directory for the server. This directory will be created if it does not exist.

    fmwRemoteServerListenAddress

    Host name of the system where the WebLogic Server for AIA is running.

    fmwRemoteServerListenPort

    Port on which the WebLogic Server for AIA is listening.

    fmwRemoteServerUserName

    Name of the user that OSM should use to connect to AIA.

    fmwRemoteServerPassWord

    Password of the user defined in the fmwRemoteServerUserName parameter.


  4. Save and close the file.

Running the config_All Target

To configure the WebLogic Server resources:

  1. Verify that Design Studio is running.

  2. From the Window menu, select Show View, and then select Other.

    The Show View window is displayed.

  3. Expand Ant and select Ant from below it. Click OK.

    The Ant view opens.

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

    The Buildfile Selection dialog box is displayed.

  5. Expand the OSM.O2A.Cartridges.Migration cartridge and expand the config directory. Add the files listed below and click OK.

    • If central order management and service order management are in the same OSM instance, add config_COMSOM.xml.

    • If central order management and service order management are in different OSM instances, add config_COM.xml and config_SOM.xml.

    The files are displayed in the Ant view. Each file is listed as with config replaced by OracleComms_OSM_O2A_CartridgeMigration. For example, if you added the config_COMSOM.xml file, it is listed as OracleComms_OSM_O2A_CartridgeMigration_COMSOM.xml in the Ant view.

  6. For each file you have added, configure the buildfile:

    1. In the Ant view, right-click the name of the 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 file and select Run As again.

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

      The Edit Configuration dialog box is displayed.

      Note:

      After you have deselected the Use global properties... check box, Eclipse prevents you from changing any of these properties until you close and reopen the Edit Configuration dialog box.
    9. Click the Properties tab and set the appropriate values listed in Table 12-11.

      Table 12-11 Values for Ant Edit Configuration Properties Tab

      Property Name Description Notes

      aia.emulator.serverName

      Name of the server within WebLogic Server to which you want to deploy the emulators. Set this to the name of the cluster if OSM is installed to a cluster or to the (administration or managed) server name if OSM is installed on a single server.

      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 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 buildfile has COM or COMSOM in the name.

      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 buildfile has COM or COMSOM in the name.

      cf.clusterName

      Name of the cluster for central order management, exactly as it is shown in the WebLogic Server console.

      Set this if the buildfile has COM or COMSOM in the name and you are in a clustered WebLogic Server 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 buildfile has COM or COMSOM in the name.

      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 buildfile has SOM in the name.

      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 buildfile has SOM in the name.

      lf.clusterName

      Name of the cluster for service order management, exactly as it is shown in the WebLogic Server console.

      Set this if the buildfile has SOM in the name and you are in a clustered WebLogic Server 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 buildfile has SOM in the name.


    10. Click Close and click Yes.

  7. For each 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 Server 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, 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 Server 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 the 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 AIA or enter p (for production environment) if you intend to connect to 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. If you selected to have a development environment, in the next Ant Input Request window, enter d to deploy the AIA emulators or enter n to skip deploying the AIA emulators.

    8. If you selected to have a production environment, in the next Ant Input Request window, enter b to install a JMS bridge to AIA or enter s to install a Store-and-Forward (SAF) service for communications with AIA.

      Note:

      If you are connecting to AIA version 11.1 or later, select s in this step. JMS bridges are not supported for communication to AIA 11.1 or later.
    9. Click OK.

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

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

    Note:

    If you have made a mistake setting the Design Studio preferences and it causes this procedure to fail, this will be displayed in the Console view in Design Studio. First, correct the preferences using the instructions in "Setting Design Studio Preferences." Next, go to the Properties tab of the Edit Configuration dialog box, select Use global properties as specified in the Ant runtime preferences to update the values, and then deselect Use global properties as specified in the Ant runtime preferences again. Then, select Clean from the Project menu and clean and build the OracleComms_OSM_O2A_Install project. Exit and restart Design Studio, and then begin the procedure for configuring the WebLogic Server resources again.
  9. If you are updating 7.0.2 cartridges, go to the WebLogic Administration Console and add the user automation with the password automation1.

Deploying the Updated Order-to-Activate 7.0.2 and 7.0.3 Cartridges

The following section provides the procedure for deploying the updated Order-to-Activate cartridges. It must be performed for 7.0.2 and 7.0.3 cartridge updates.

Before deploying the Order-to-Activate cartridges:

To deploy the updated Order-to-Activate cartridges:

  1. Verify that Design Studio is running.

  2. Create a new Studio Environment project and a new Studio environment.

    Note:

    See the Design Studio Help for details on creating a Studio Environment project and a Studio environment.

    If you are installing central order management and service order management on different OSM servers, you need two environment entities: one pointing to the central order management cluster or standalone server and the other pointing to the service order management cluster or standalone server.

  3. Open the Environment perspective.

  4. Select the Design Studio environment in which the cartridges are to be deployed.

    The Cartridge Management pane is displayed, displaying a list of available cartridges.

  5. Select all of the cartridges you wish to deploy and click Deploy.