7 Configuring Service Orchestration

This chapter describes how to configure service orchestration in Oracle Communications Service Controller.

About Service Orchestration

Service Controller can invoke one or more applications, combining and delivering multiple services to sessions in the network. Service orchestration is performed by the Orchestration Engine based on an orchestration logic which defines how to route sessions through a number of applications. The Orchestration Engine invokes the applications in a particular order, according to conditions in the orchestration logic that determine which applications to invoke and in what order.

To create the orchestration logic you use the Orchestration Studio. See Oracle Communications Service Broker Orchestration User's Guide for information about the Orchestration Studio and how to use it to define an orchestration logic.

After you create the orchestration logic, you store it as part of the subscriber's profile. Whenever Service Controller handles a session, it first obtains the profile of the subscriber that owns the session, and then route the session according to the orchestration logic in that profile. Service Controller support the following subscriber profile stores:

• Local Subscriber Server (LSS), which is an on-board implementation of a profile server. The LSS is capable of storing subscriber profiles, including orchestration logic given in the Initial Filter Criteria (iFC) format. The LSS is implemented as a supplementary module named SM-LSS. See the chapter about SM-LSS in Oracle Communications Service Broker Modules Configuration Guide for information about configuring the LSS.

• Home Subscriber Server (HSS), which is the standard primary user database in the IMS domain. Service Controller uses a standard Diameter Sh interface to connect the HSS obtain the orchestration logic.

When you configure Service Controller you choose only one of the subscriber profile store options. You define which subscriber store you use in the Orchestration Engine, and configure fields in the Orchestration Engine configuration screens that are relevant to the subscriber store of your choice.

It is possible to configure the Orchestration Engine to route all sessions through one or more applications that you define, without using an orchestration logic, and without going to the LSS or HSS to obtain the orchestration logic. See "Using Static Service Orchestration" for more information.

Using Static Service Orchestration

When you configure a static service orchestration, Service Controller routes all session through one or more applications that you define, without using any orchestration logic, and without turning to a subscriber profile store, such as LSS and HSS, to obtain the orchestration logic.

To configure a static service orchestration, in the Administration Console:

1. In the navigation tree, expand the OCSB node.

2. Expand the Processing Tier node, and then the Orchestration Engine node.

3. In the Configuration tab, select the General tab.

4. In the Subscriber Profile Receiver list, select OlpDefaultInfoReceiver.

5. In the Configuration tab, select the Static Route OLP tab.

6. In the Default Routing Targets field, enter a list of alpha-numeric addresses of target applications. For each application enter sip:[e-mail], where module is the name of the interworking module that enables the connection with the target application, and type is type of the module.

   For example, sip:[e-mail]

   Use the space character to separate between two target applications in the list.

Using Orchestration Logic in the LSS for Service Orchestration

When you choose LSS to be your profile database, you create the service orchestration logic using the Orchestration Studio, store the orchestration logic under the subscriber profile in the LSS, and configure the Orchestration Engine to obtain orchestration logic from the LSS.

To configure orchestration logic in the LSS for Service Orchestration:

1. Define a new profile in the LSS:

   1. In the Administration Console, in the navigation tree, expand the OCSB node.

   2. Expand the Processing Tier node, and then the Supplementary Modules node.

   3. Select the SM-LSS node.

   4. In the Configuration tab, select the Orchestration Profiles tab.

   5. Click New button. The New dialog box appears.

   6. Enter the fields in the New dialog box as described in the section about configuring orchestration profiles, in the chapter about configuring SM-LSS, in Oracle Communications Service Broker Modules Configuration Guide.

   7. Click Apply.

2. Use the Orchestration Studio to define the orchestration logic for the new profile that you defined in step 1. In the Orchestration Studio, from the iFC list, select the name of the profile. Define an orchestration logic and save it. See Oracle Communications Service Broker Orchestration User's Guide for information about using the Orchestration Studio to define an orchestration logic.

3. Configure the Orchestration Engine to use the LSS for its subscriber profile store.

   1. In the Administration Console, in the navigation tree, expand the OCSB node.

   2. Expand the Processing Tier node, and then select the Orchestration Engine node.

   3. In the Configuration tab, select the General tab.

   4. In the Subscriber Profile Receiver list, select OlpLSSInfoReceiver.

Using Orchestration Logic in an HSS for Service Orchestration

When you choose an external HSS for your profile database, you configure the Orchestration Engine to use the service orchestration logic stored under the profiles in the HSS.

To configure the Orchestration Engine to use the HSS for its subscriber profile store:

1. In the Administration Console, in the navigation tree, expand the OCSB node.

2. Expand the Processing Tier node, and then select the Orchestration Engine node.

3. In the Configuration tab, select the General tab.

4. In the Subscriber Profile Receiver list, select OlpHSSInfoReceiver.

5. In the Configuration tab, select the HSS OLP tab.

6. The interface with the HSS is a standard Diameter Sh interface. Use the Destination-Host AVP and Destination-Realm AVP fields to configure the address of the HSS.

   If you previously defined the HSS as an outbound destination in the SSU Diameter, you can enter the alias of the outbound destination in the Destination-Host AVP field.

To provision orchestration logic in the HSS, you use tools provided with the HSS. To define orchestration logic that you later provision in the HSS, you can use the Orchestration Studio. In the Orchestration Studio, from the iFC list, select default. Use the Orchestration Studio's tools to define and edit the orchestration logic. Once the orchestration logic is ready, you can use the generated iFC to provision it in the HSS.

Updating the Service Orchestration Chain

After you create an orchestration chain and store it, you can update it to add applications to the chain, remove applications from the chain, change application invocation criteria and so on.

The procedure for updating the service orchestration chain depends on the method that you use for service orchestration; that is, static service orchestration, orchestration logic in the LSS, or orchestration logic in the HSS.

You can use the Service Controller graphical user interface to change a static service orchestration or the orchestration logic stored in the LSS. If you use HSS to store orchestration logics, you need to use the tools provided with the HSS to change the orchestration logic that it stores.

Updating the Static Orchestration Chain

To add or remove an application from the a static orchestration chain:

1. In the Administration Console, in the navigation tree, expand the OCSB node.

2. Expand the Processing Tier node, and then select the Orchestration Engine node.

3. In the Configuration tab, select the Static Route OLP tab.

4. In the Default Routing Targets field, either add the alpha-numeric address of an application to the list of applications, or remove an address from the list. If you add an address, enter sip:[e-mail], where module is the name of the module that enables the connection with the target application, and type is type of that module.

Updating the Orchestration Logic in the LSS

To update the orchestration logic of a profile stored in the LSS, in the Orchestration Studio, from the iFC list, select the name of the LSS profile whose orchestration logic you want to change. Update the orchestration logic and save it.

Updating the Orchestration Logic in the HSS

To update the orchestration chain stored in the HSS, use the tools provided with the HSS to change the orchestration logics. Alternatively, you can use the default orchestration profile in the Orchestration Studio to define the updated orchestration logic. Then, to provision the updated orchestration logic in the HSS, you use tools provided by the HSS.