6 Invoking Applications Based on the Previous Session Route

This chapter describes how to use the Oracle Communications Service Broker Orchestration Studio to set up an application to run based on the previous route of the session.

About Invoking Applications Based on the Previous Session Route

You can set up an application to run based on the previous route of the session. For example, you can set up a pre-paid application to run only if the session contains tags indicating that a home zone application precedes the pre-paid application in the orchestration chain.

To enable applications in the orchestration chain to get the information about applications through which the session is routed, you need to tag the session when it passes through an application. For example, if the OE routes the session to a home zone application, you can tag the session with the tag HomeZoneAppInvoked. This allows next applications in the orchestration chain to be aware of the hoe zone application was triggered.

Then you can set up one of the next applications in the chain (such as a bill shock prevention application) to run only if the session contains the HomeZoneAppInvoked tag.

As the session passes through applications in the orchestration chain, all tags are accumulated. Therefore, any subsequent application in the orchestration chain can be aware of those tagged applications which were previously triggered.

The OE adds tags to the session when routing it to the IM defined in the orchestration logic. You define a tag to be added as a part of the configuration of the appropriate IM.

Note:

Service Broker does not support tags when the Diameter-based orchestration mode is enabled. For more information on the Diameter-based orchestration mode, see the discussion on improving performance in Diameter-only environments in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.

Tagging a Session

To tag a session:

1. Select the IM icon of the IM that communicates with the application.

2. Click the Actions tab.

3. Click Add.

4. In the New dialog box, type the name of the tag you want to associate with the selected application and click OK.

   The tag name you defined is displayed in the Tag field. The Header field displays x-wcs-tags. This is the header that contains tags. You cannot modify the name of the header.

Checking Tags in a Session

You can set up an application to run depending on the application through which the session has already passed. For example, you can set up a condition that invokes the following applications in the chain:

• Home zone

• VPN

• Online charging

If, for example, the session does not contain a tag specifying it should access the VPN application, it skips the VPN application and continues to the pre-paid application.

You set up tags on a condition only when its icon is preceded by the IM icons representing the applications that added the specified tags to the session.

To set up tags on a condition:

1. Select the Conditions icon in the flow to which you want to apply a tag.

2. Click the Actions tab.

3. Select the group under which you want to apply the tag.

4. Click Tag.

   The Header field displays x-wcs-tags. This is the name of the header that contains tags added by the applications to the session. You cannot modify this text.

5. In the Content field, add the tag of the application to which you want the session to be routed.

   You can add as many tags as required, separated by a comma and a space.

   You can use regular expressions. For example, if your tag is .*1234.* the message is routed to all numbers that contain 1234, regardless of the numbers that precede or succeed it.