6 Performing Order-to-Activate Cartridge Operations

This chapter describes operational procedures that may be needed for the Order-to-Activate cartridges for Oracle Communications Order and Service Management (OSM).

XQuery Transformation Logging

To enable or disable logging for XQuery transformations, use the log4jAdmin page. See the section on configuring severity levels in the Monitoring and Managing OSM chapter in OSM System Administrator's Guide for more information about using the log4jAdmin page. The following information will help you when looking at the generic information about using log4jAdmin that is located there:

  • If you want to set the logging level temporarily, first run an order that calls the XQuery transformation that you want to log. This ensures that the EJB that runs it is loaded. Otherwise you may not find the appropriate logger on the log4jAdmin page.

  • To find the logger for the XQuery transformation that you want to change, look at the name formats below and look up the relevant information in Oracle Communications Design Studio.

    • If the automation is an external event receiver, the logger will be listed with a name like this:

      /automation/plugin/external/SolutionCartridgeName/SolutionCartridgeVersion/TaskOrEventName.EJBName

      For example:

      /automation/plugin/external/OracleComms_OSM_O2A_COMSOM_TypicalSolution/2.0.1.2.0/FulfillBillingSITask.FulfillBillingResponseBean

    • If the automation is an internal event receiver, the logger will be listed with a name like this:

      /automation/plugin/internal/AutomationType/SolutionCartridgeName/SolutionCartridgeVersion/AutomationEntityName/CompensationMode

      where /CompensationMode is only included for task automations.

      For example:

      /automation/plugin/internal/task/OracleComms_OSM_O2A_COMSOM_TypicalSolution/2.0.1.2.0/FulfillBillingEntryPointTask/do_redo_undo

Enabling or Disabling Product Attribute Validation

By default, central order management orders are validated to ensure that product attributes are present on the order, and the order is failed if the validation is not present. You can disable this validation as long as the order will not create assets. This validation is not performed on service order management orders.

This validation is enabled or disabled using a model variable on the solution cartridge. Table 6-1 lists which solution cartridge applies, depending on your situation. In environments that contain both central order management and service order management orders, only central order management orders are validated.

Table 6-1 Solution Configurations and Corresponding Solution Cartridges

Using Calculate Service Order Option? Current Workspace Is for: Topology Solution Cartridge

Yes

COM only

All

OracleComms_OSM_O2A_COM_CSO_Solution

Yes

COM and SOM

All

OracleComms_OSM_O2A_COMSOM_CSO_Solution

No

COM only

Simple

OracleComms_OSM_O2A_COM_Simple_NP_Soln

No

COM only

Typical or Complex

OracleComms_OSM_O2A_COM_Typical_NP_Soln

No

COM and SOM

Simple

OracleComms_OSM_O2A_COMSOM_Simple_NP_Soln

No

COM and SOM

Typical or Complex

OracleComms_OSM_O2A_COMSOM_Typical_NP_Soln

The model variable is ENABLE_PRODUCT_ATTRIBUTE_VALIDATION, and its possible values and their meanings are:

  • enable: (default) OSM will validate the input central order management order, and fail order creation if the validation fails.

  • disable:

    • If this asset processing is enabled, and the current order would create assets, the behavior is the same as enable.

    • If asset processing is not enabled or the services on the order would not create any assets, OSM will not fail order creation if the data on the order does not correspond with the data for the products.

For information about setting model variables, see the information about working with Design Studio cartridge projects in the Design Studio Help.

Troubleshooting Order-to-Activate Cartridges

The following procedures can help you in troubleshooting the Order-to-Activate cartridges.

Updating the JMS Redelivery Configuration Settings

When the Order-to-Activate cartridges are installed, the Redelivery Delay Override and Redelivery Limit WebLogic parameters are set during installation to 7000ms and 10, respectively. However, different values may be more effective for your OSM environment depending on your usage of the system.

If you encounter timing-related issues for message delivery on JMS queues, there are a number of WebLogic settings that you can modify to resolve the issue. These values are set on every JMS queue through the WebLogic Service Console. From Home, select JMS Modules, and then select oms_jms_module to modify the following settings:

  • Redelivery Delay Override: Delay in milliseconds before rolled back or recovered messages are redelivered. This value overrides the Redelivery Delay setting.

  • Redelivery Limit: The number of times to attempt to redeliver a message.

To find the best values for these parameters, start with initial values less than 7000ms for the Redelivery Delay Override and 10 for the Redelivery Limit and increase them slightly until no occurrences of errors are observed. The actual values you finalize on will depend on your particular implementation of OSM. See the Oracle WebLogic documentation for complete details on these parameters.

Setting Cartridge Breakpoints

There are process flows in the cartridge with a manual task between each automated task. With certain input data in the customer order, it causes it to go through the automation and stop at a particular manual task.

The Order-to-Activate cartridges have been instrumented with control points in the process flows so that a tester can control the process flow before or after functions, examine data anywhere in the flow, do revision testing, and do point-of-no-return testing. The flows are automated, but can be instructed to stop at a manual task before or after normal automated tasks.

The Siebel Customer Relationship Management (Siebel CRM) sales order number is used to control the flows by prefixing the number with format [AIATest.Task#.Target#]. Only one breakpoint can be set.

Table 6-2 lists the task numbers and names.

Table 6-2 Task Number and Task Name

Task # Task Name

0

Any

1

Before SyncCustomer Task

2

Before InitiateBilling Task

3

Before FulfillBilling Task

7

After SyncCustomer Task

8

After InitiateBilling Task

9

After FulfillBilling Task

10

After Provisioning Request Sent Task

11

After Provision Response Received Task

31

Before Provision InternetServiceBundle Task

32

Before Provision InternetMediaServiceBundle Task

33

Before Provision InternetEmailServiceBundle Task

34

Before Provision CPEEntryPointTask

41

Before Provision VoIPServiceBundle Task

42

Before Provision VoIPCPE Task

Table 6-3 lists the OSM and Oracle Application Integration Architecture (Oracle AIA) fulfillment systems.

Table 6-3 OSM and Oracle AIA Targets

Target# OSM Fulfillment System Name AIA Logical Fulfillment System ID

0

Any

Any

1

BRM-ALL

BRM_01

2

BRM-VoIP

BRM_02

4

BRM-REZBDB

BRM_03

4

BRM-BIZBDB

BRM_04

7

Provisioning-ALL

OSMPROV_01

8

Provisioning-VoIP

OSMPROV_02

9

Provisioning-VoIP

OSMPROV_02

10

Provisioning-BRD

OSMPROV_03

It is also possible to disable the PoNR per-component level by setting the order key prefix as [PONRControl.Component#].

Table 6-4 lists the OSM component levels.

Table 6-4 OSM Component levels

Component # OSM Component Name Example

0

Any

[PONRControl.0]

1

SyncCustomerFunction

[PONRControl.1]

2

InitiateBillingFunction

[PONRControl.2]

3

ProvisionOrderFunction

[PONRControl.3]

4

ShipOrderFunction

[PONRControl.4]

5

InstallOrderFunction

[PONRControl.5]

6

FulfillBillingFunction

[PONRControl.6]

7

InstallOrderFunction ShipOrderFunction

[PONRControl.7]

8

ProvisionOrderFunction,

InstallOrderFunction,

ShipOrderFunction

[PONRControl.8]