4 Using Subscriber Account Lifecycles

This chapter describes how to customize subscriber account lifecycle states, which represent the status of subscriber accounts in the Oracle Communications Service Broker Subscriber Store.

About Subscriber Account Lifecycle States

The lifecycle state value in the subscriber profile represents the state of the account associated with a particular subscriber. External systems can set and read the lifecycle state of a subscriber through the Subscriber Provisioning API.

The account lifecycle state is an element in the subscriber profile data model. Its value appears in the accountState element, which is a child element of globalProfileData. See "Subscriber Profile Data Model" for more information about profile data.

The Service Broker processing domain configuration includes predefined lifecycle states. The default states correspond to typical account states in a network subscriber repository. However, you should modify these values to match those used by the systems in your environment that will interact with Service Broker, such as your existing OCS.

The default lifecycle states are:

• Pre-Active

• Active

• Suspended

• Locked

• Deactivated

The Subscriber Provisioning API service validates the state values submitted in subscriber create or update requests. However, while the Subscriber Provisioning service validates and maintains state values in the Subscriber Store, Service Broker does not otherwise interpret the meaning of a particular state value. It is the role of the back end system to associate a particular state with service provisioning logic.

Adding a Lifecycle State

To add a lifecycle state:

1. In the Domain Navigation pane, expand the OCSB node.

2. Expand the Processing Tier node.

3. Expand the Subscriber Store node.

4. Click the Data Validation item.

5. In the Account Lifecycle tab, click the New button.

6. Enter the account state value in the Lifecycle State field.

7. Click OK.

The new state appears in the list of lifecycle states. After you commit the changes to the running configuration, the Subscriber Provisioning Service will accept the account state value you configured.

To use JMX MBeans to add a lifecyle state, use the addState operation in the lifecycleConfigMBean, which has the following object name:

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.service.subscriber_store.datavalidation,version=6.0.0.SNAPSHOT,name0=lifecycleConfig

Changing a Lifecycle State

To change a lifecycle state:

1. In the Domain Navigation pane, expand the OCSB node.

2. Expand the Processing Tier node.

3. Expand the Subscriber Store node.

4. Click the Data Validation item.

5. In the Account Lifecycle tab, select the state you want to modify in the State Configuration list.

6. Click the Update button.

7. Enter the new value in the Lifecycle State field and click OK.

The renamed state appears in the list of lifecycle states.

To use JMX MBeans to modify a lifecyle state, edit the name attribute value for the MBean instance of the state you want to change under the lifecycleConfigMBean, which has the following object name:

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.service.subscriber_store.datavalidation,version=6.0.0.SNAPSHOT,name0=lifecycleConfig

Deleting a Lifecycle State

To remove a lifecycle state:

1. In the Domain Navigation pane, expand the OCSB node.

2. Expand the Processing Tier node.

3. Expand the Subscriber Store node.

4. Click the Data Validation item.

5. In the Account Lifecycle tab, select the state you want to remove in the State Configuration list.

6. Click the Delete button.

7. Confirm the operation by clicking OK.

The removed state is removed from the list of lifecycle states.

To use JMX MBeans to remove a lifecyle state, use the removeState operation in the lifecycleConfigMBean, which has the following object name:

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.service.subscriber_store.datavalidation,version=6.0.0.SNAPSHOT,name0=lifecycleConfig

When invoking the operation, pass the instance number that corresponds to the state to remove.