7 Configuring PCP Signaling Server Units

This chapter describes how to configure the Service Broker Portal Communications Protocol (PCP) Signaling Server Unit (SSU) using the Service Broker Administration Console and Java MBeans.

About the PCP SSU

Service Broker acts as an Oracle Communications BRM client application and uses the PCP SSU to communicate with it. The communication is done through a proprietary Oracle Communications BRM protocol, the PCP.

The PCP SSU receives charging requests from internal Service Broker components, such as IM-OFCF PCP and IM-OCF PCP, and routes these request to BRM applications through PCP.

To access Oracle Communications BRM, the PCP SSU must use a BRM client application account. The PCP SSU uses the default root account created when BRM is installed, and its password. See "Configuring Login Names and Passwords for BRM Access" in the chapter "Implementing System Security" in Oracle Communications Billing and Revenue Management System Administration Guide.

The PCP SSU uses connection pools to communicate with BRM. A connection pool is a set of connections maintained between the PCP SSU and the BRM Connection Manager (CM). Each Oracle Communications BRM CM is running on a different physical address and listens to PCP request on a different port. See "About Connection Pooling" in Oracle Communications Billing and Revenue Management System Administration Guide. On the BRM side, an incoming request is assigned a connection from the connection pool and uses the connection to perform operations. When the operation completes, the connection is returned to the pool.

When configuring the PCP SSU connectivity with BRM, you define a number of connection pools, each communicates with one CM. Oracle recommends that you define two or more connection pools, for redundancy and high availability.

Connection pools need to be secured with passwords. You set a password in both the PCP SSU and Oracle Communications BRM. You have to configure the same password for a connection pool that you define in the PCP SSU, and the related CM that you configure on Oracle Communications BRM.

Each connection pool is considered a PCP network entity. If one or more PCP network entities act as one logical Oracle Communications BRM application, you assign one alias to those network entities. Service Broker IMs sending PCP requests to an Oracle Communications BRM application, use the alias to specify the destination BRM application. The PCP SSU routing the requests to their destination, provides a measure of redundancy, distributing the PCP requests among the different PCP network entities belonging to the same destination BRM application.

The PCP SSU implements a heartbeat mechanism, regularly sending requests to PCP network entities to check their availability. Not receiving a response within a configured time interval denotes that the PCP network entity is inactive. The PCP SSU stops sending requests to inactive network entities, but continues checking their availability every few seconds. You configure the heartbeat mechanism for each PCP network entity separately, when you define the network entity.

After configuring connection pools and destination Oracle Communications BRM applications, you can also optionally change the default configuration of PCP transactions.

Configuring PCP Transactions

You use either the Administration Console or Java MBeans to configure PCP transactions.

Configuring PCP Transactions with the Administration Console

To configure PCP Transaction:

1. In the navigation tree in the domain navigation pane, expand the OCSB node.

2. Expand the Signaling Tier node.

3. Select the SSU PCP node.

4. In the PCP tab, select the Opcode tab.

5. Enter the fields described in Table 7-1.

   Table 7-1 Opcodes Parameters

   Field	Descriptions
   opcodeRetry	Specifies the number of attempts that the PCP SSU tries to execute a BRM opcode. Default value: 3
   opcodeTimeout	Specifies the opcode timeout by default Default value: 5000
   pcpTransactionIdleTimeout	Specifies the PCP transaction timeout. Default value: 10000

   
   

Configuring PCP Transactions with Java MBeans

Figure 7-1 shows the hierarchy of the configuration MBeans that you use to configure PCP transactions. See "PCP SSU Configuration MBeans Reference" for the object names of these MBeans.

Figure 7-1 Opcodes Configuration MBeans

To configure opcodes:

1. Create an instance of OpcodeRetryMBean by invoke the following operation of pcpConfigMBean:

   void addOpcodeRetry()
   

   The new instance of opcodeRetryMBean is created.

2. Set the opcodeRetry attribute of opcodeRetryMBean as described in Table 7-1.

3. Set the opcodeTimeout attribute of opcodeTimeoutMBean as described in Table 7-1.

4. Create a new instance of PcpTransactionIdleTimeoutMBean by invoking the following operation of pcpConfigMBean:

   void addPcpTransactionIdleTimeout()
   

   The new instance of pcpTransactionTimeoutMBean is created.

5. Set the pcpTransactionTimeout attribute of pcpTransactionTimeoutMBean as described in Table 7-1.

Setting Up Connection Pools

To set up a connection pool:

1. Define the connection pool. See "Defining Connection Pools".

2. Secure the connection pool. See "Securing Connection Pools". After securing the connection pool, you can further manage the connection pool credentials. See "Managing Connection Pool Credentials".

Defining Connection Pools

To define a connection pool you need to specify the physical address and port of the Oracle Communications BRM CM providing connections, and a assign an identifier, that is a Pool ID, to the connection.

You configure connection pools using either the Administration Console or Java MBeans.

Configuring Connection Pools with the Administration Console

To configure connection pools:

1. In the navigation tree in the domain navigation pane, expand the OCSB node.

2. Expand the Signaling Tier node.

3. Select the SSU PCP node.

4. In the PCP tab, select the Connection Pools tab.

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

6. Enter the fields described in Table 7-2.

   Table 7-2 Connection Pool Parameters

   Field	Descriptions
   Pool ID	A unique connection pool identifier.
   BRM CM Host	The name or IP address of the machine running the Oracle Communications BRM CM. See "Using Configuration Files to Connect and Configure Components" in Oracle Communications Billing and Revenue Management System Administrator's Guide.
   BRM CM Port	The port number of the Oracle Communications BRM CM on the host machine. See "Using Configuration Files to Connect and Configure Components" in Oracle Communications Billing and Revenue Management System Administrator's Guide.
   BRM CM Login ID	account-name.database-number Where: account-name is the name of the BRM client application account that Service Broker uses to access Oracle Communications BRM. See "Configuring Login Names and Passwords for BRM Access" in the chapter "Implementing System Security" in Oracle Communications Billing and Revenue Management System Administrator's Guide. database-number is the database number that you configured when you installed the BRM application. Default value: root.0.0.0.1 See "Installing BRM" in Oracle Communications Billing and Revenue Management Installation Guide.
   Maximum Connections	Specifies the maximum number of connections in the pool. Default value: 8
   Minimum Connections	Specifies the minimum number of connections in the pool. Default value: 4
   Request Timeout	Specifies the time that the PCP SSU waits for establishing a connection.
   Maximum Idle Time	Specifies the maximum idle time for a connection. When the specified time expires, the PSP SSU closes the connection.
   Request Queue Size	Specifies the maximum size of the queue. When the maximum size is reached, the PCP SSU drops all further requests.
   Enabled	Specifies whether the connection is enabled. You can use this field to disable a connection pool, for example, for maintenance. Possible values: true false Default value: true

   
   

Configuring Connection Pools with Java MBeans

Figure 7-2 shows the configuration MBeans that you use to configure BRM connections. See "PCP SSU Configuration MBeans Reference" for the object names of these MBeans.

Figure 7-2 Connection Pools Configuration MBeans

Each connection is represented by connectionPoolConfigMBean. You need to create a separate instance of connectionPoolConfigMBean for each connection. After you created an instance of connectionPoolConfigMBean, you can create its child MBeans. Each of these child MBeans represents a specific parameter of the connection. For example, cmPoolIdMBean has the attribute cmPoolId which represents the Pool ID parameter.

All connections are grouped and represented by connectionPoolsMBean.

To create a connection:

1. Create an instance of connectionPoolsMBean by invoking the following operation of pcpConfigMBean:

   void addConnectionPools()
   

   The new instance of connectionPoolsMBean is created.

2. Create a instance of connectionPoolConfigMBean by invoking the following operation of connectionPoolsMBean:

   void addConnectionPoolConfig()
   

   The new instance of connectionPoolMBean with a set of child MBeans is created.

3. Set the attributes of the child MBeans as described in Table 7-3.

   Table 7-3 BRM Connection Child MBeans Attributes

   MBean	Attribute
   cmPoolIdMBean	cmPoolId
   hostMBean	host
   portMBean	port
   loginMBean	login
   cmPoolMaxSizeMBean	cmPoolMaxSize
   cmPoolMinSizeMBean	cmPoolMinSize
   cmPoolTimeoutMBean	cmPoolTimeout
   cmPoolMaxIdleTimeMBean	cmPoolMaxIdleTime
   cmPoolMaxRequestQueueSizeMBean	cmPoolMaxRequestQueueSize
   enabledMBean	enabled

   
   

Securing Connection Pools

To access the BRM using a connection pool, the PCP SSU is using a BRM client application account. You configure the BRM client application name when you set up a connection pool. You use the PCP SSU Credential Store to configure and save the BRM client application password.

You must specify a password for each connection pool. The password you configure is the password of the BRM client application account used by the connection pool to access the BRM.

You can set up connection pool passwords using the Administration Console or Java MBeans.

Setting Up a Connection Pool Password with the Administration Console

To set up a connection pool password:

1. In the navigation tree in the domain navigation pane, expand the OCSB node.

2. Expand the Signaling Tier node.

3. Select the SSU PCP node.

4. In the PCP tab, select the Credential Store tab.

5. In the Password area, enter in the fields described in Table 7-4:

   Table 7-4 Connection Pool Password

   Field	Descriptions
   Key	A connection pool identifier. The identifier that you assigned to the connection pool, in the field Pool ID, when you initially defined the connection pool.
   Password	The password of the BRM client application account used by the connection pool to access the BRM. This is the password of the account that you configured in the BRM CM Login ID, when you initially defined the connection pool.
   One-way	Always uncheck this box. The PCP SSU should be able retrieve the connection pool password from the Credential Store and use it when sending requests to Oracle Communications BRM.

   
   

6. Click the Set Password button.

Setting Up a Connection Pool Password with Java MBeans

Figure 7-3 shows the hierarchy of the configuration MBeans that you use to set up the password for connections to BRM applications. See "PCP SSU Configuration MBeans Reference" for the object names of these MBeans.

Figure 7-3 BRM Connection Passwords Configuration MBeans

To set up the password:

1. Invoke the following operation of CredentialStoreMBean:

   void setPassword (string Key, string Password, boolean One-way)
   

   See Table 7-4 for more information about these parameters.

2. Invoke the following operation of CredentialStoreMBean:

   boolean validatePassword()
   

Managing Connection Pool Credentials

You can check whether a key exists in the Credential store and delete keys. You can manage keys using the Administration Console or Java MBeans.

Managing Credential Store Keys with the Administration Console

You can check whether a key exists in the Credential store and delete keys.

To check whether a key exists in the credential store:

1. In the navigation tree in the domain navigation pane, expand the OCSB node.

2. Expand the Signaling Tier node.

3. Select SSU PCP node.

4. In the PCP tab, click the Credential Store tab.

5. In the General area, in the Key field, enter the key whose existence you want to check.

6. Click Contains Key?.

   The message which informs you whether the key exists, appears.

7. To close the message, click OK.

To delete a a specified key from the credential store:

• In the Credential Store tab, in the General area, in the Key field, enter the key and then click Delete Key.

To delete a all keys from the credential store:

• In the Credential Store tab, in the General area, click Delete All Keys.

Managing Keys in the Credential Store with Java MBeans

To manage keys in the credential store with Java MBeans, you use the same MBeans as described in "Setting Up a Connection Pool Password with Java MBeans".

To check whether a key exists in the credential store:

• Invoke the following operations of CredentialStoreMBean:

  boolean containsKey (string Key)
  

To delete a specified key from the credential store:

• Invoke the following operations of CredentialStoreMBean:

  void deleteKey (string Key)
  

To delete all keys from the credential store:

• Invoke the following operations of CredentialStoreMBean:

  void clear ()
  

Defining PCP Network Entities

You define PCP network entities using either the Administration Console or Java MBeans.

Defining PCP Network Entities with the Administration Console

To define a PCP network entity:

1. In the navigation tree in the domain navigation pane, expand OCSB.

2. Expand the Signaling Tier node.

3. Select the SSU PCP node.

   The PCP SSU configuration pane appears. This pane displays a table listing PCP network entities. Each row represents one PCP network entity.

4. To define a new PCP network, at the bottom of the PCP SSU configuration pane, click the New button.

   The New dialog box appears.

5. Fill in the fields described in Table 7-5.

   Table 7-5 PCP SSU Parameters

   Field	Description
   Name	A unique name that you give to the PCP network entity.
   Alias	An alias that you assign to the PCP network entity. This alias is used by IMs to specify the destination of PCP requests. If two or more PCP network entities belong to the same BRM application, you assign the same alias to all of them. The PCP SSU distributes requests among network entities having the same alias. For information on how to use the alias in IMs, see "Configuring Diameter Credit Control Application Parameters" in "Configuring IM-OCF PCP" of the Oracle Communications Service Broker Processing Domain Configuration Guide "Configuring Call Handling Parameters" in "Configuring IM-OFCF PCP" of the Oracle Communications Service Broker Processing Domain Configuration Guide
   Connection Pool ID	The identifier of the connection pool used to communicate with the remote PCP network entity. This should be one of the connection pools that you have previously defined. See "Defining Connection Pools"
   Heartbeat	Specifies whether or not the PCP SSU activates the heartbeat mechanism over the connection with the network entity.
   Response Timeout	The time interval, in seconds, during which the PCP SSU waits for a response from the network entity. If the PCP SSU does not receive a response within this time interval, then it considers the network entity inactive.
   Active Interval	The time interval, in seconds, between two consecutive heartbeat requests sent to the network entity. This time interval is valid so long the network entity is considered active.
   Inactive Interval	The time interval, in seconds, between two consecutive heartbeat requests sent to the network entity. This time interval is valid so long the network entity is considered inactive.

   
   

Defining PCP Network Entities with Java MBeans

Figure 7-4 shows the hierarchy of the configuration MBeans that you use to configure PCP network entities. See "PCP SSU Configuration MBeans Reference" for the object names of these MBeans.

Figure 7-4 PCP SSU Configuration MBean Hierarchy

Each network entity is represented by PcpNetworkEntityMBean. You need to create a separate instance of PcpNetworkEntityMBean for each entity.

To create a network entity:

1. Create a new instance of PcpNetworkEntityMBean by invoking the following operation of the PcpNetworkEntitiesMBean:

   ObjectName createPcpNetworkEntity(string NetworkEntityName)
   

2. Set the following attributes of the newly created instance of PcpNetworkEntityMBean:

   • Name

   • Alias

   • PcpPoolId

   • Heartbeat

   • ResponseTimeout

   • ActiveInterval

   • InactiveInterval

   See Table 7-5 for more information about these attributes.

PCP SSU Configuration MBeans Reference

The following sections provide reference information for the PCP SSU configuration MBeans.

Note:

MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.

---

PcpSsuMBean

PcpSsuMBean is a root MBean for configuring the PCP SSU.

Object Name

com.convergin:Type=PcpSsu,Version=MBean_Version,Location=AdminServer,Name=ssupcp.ssupcp

Factory Method

Created automatically

Attributes

None

Operations

ObjectName getPcpNetworkEntities()

Returns a reference to the instance of PcpNetworkEntitiesMBean

---

PcpNetworkEntitiesMBean

PcpNetworkEntitiesMBean is the root MBean for defining BRM applications to which the PCP SSU routes a request. Using PcpNetworkEntitiesMBean, you need to create a separate instance of PcpNetworkEntityMBean for each BRM application.

Object Name

com.convergin:Type=PcpNetworkEntities,Version=MBean_Version,Location=AdminServer,Name=ssupcp.pcp_outbound_routing

Factory Method

Created automatically

Attributes

None

Operations

ObjectName getPcpNetworkEntity()

Returns a reference to the instance of PcpNetworkEntityMBean

ObjectName createPcpNetworkEntity()

Creates an instance of PcpNetworkEntityMBean

void destroyPcpNetworkEntity()

Destroys an instance of PcpNetworkEntityMBean

ObjectName lookupPcpNetworkEntity()

Searches for an instance of PcpNetworkEntityMBean

---

PcpNetworkEntityMBean

PcpNetworkEntityMBean enables you to define the BRM application to which the PCP SSU routes a request. You need to create a separate instance of PcpNetworkEntityMBean for each BRM application.

Object Name

com.convergin:Type=PcpNetworkEntity,Version=MBean_Version,Location=AdminServer,Name=ssupcp.PcpNetworkEntityName

Factory Method

Created automatically

Attributes

• Alias

• Heartbeat

• ResponseTimeout

• ActiveInterval

• InactiveInterval

• PcpPoolId

For more information about these attributes, see Table 7-5.

Operations

None

---

CredentialStoreMBean

CredentialStoreMBean enables you to set up passwords for BRM connections and the credential store. In addition, you can use CredentialStoreMBean to manage keys in the credential store.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc. protocol_adapter.pcp.adapter,version=MBean_Version,name0=CredentialStore

Factory Method

Created automatically

Attributes

None

Operations

void setPassword()

Sets a password for the specified key

boolean validatePassword()

Validate a password against a password stored for the specified key

void setKeystore()

Validate a password against a password stored for the specified key

boolean containsKey()

Return true if the key exists in the credential store

void deleteKey()

Delete a key

void clear()

Remove all entries

---

pcpConfigMBean

pcpConfigMBean is the root MBean for configuring BRM connection pools.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc. protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig

Factory Method

Created automatically

Attributes

None

Operations

void addConnectionPools()

Add a new 'connectionPools' Element

void removeConnectionPools()

Add a new 'connectionPools' Element

void addOpcodeRetry()

Add a new 'opcodeRetry' Element

void removeOpcodeRetry()

Remove the 'opcodeRetry' Element

void addPcpTransactionIdleTimeout()

Add a new 'pcpTransactionIdleTimeout' Element

void removePcpTransactionIdleTimeout()

Remove the 'pcpTransactionIdleTimeout' Element

---

connectionPoolsMBean

connectionPoolsMBean is the root MBean for configuring connections with BRM applications.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools

Factory Method

pcpConfig.addConnectionPools()

Attributes

None

Operations

void addConnectionPoolConfig()

Add a new 'connectionPoolConfig' Element

void removeConnectionPoolConfig()

Remove the 'connectionPoolConfig' Element whose id is in connectionPoolConfig(...)

---

connectionPoolConfigMBean

connectionPoolConfigMBean represents a single connection with a BRM application.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex]

Factory Method

connectionPools.addConnectionPoolConfig()

Attributes

None

Operations

void cloneIt()

Clone the current element

void addCmPoolMaxSize()

Add a new 'cmPoolMaxSize' Element

void removeCmPoolMaxSize()

Remove the 'cmPoolMaxSize' Element

void addCmPoolMinSize()

Add a new 'cmPoolMinSize' Element

void removeCmPoolMinSize()

Remove the 'cmPoolMinSize' Element

void addCmPoolTimeout()

Add a new 'cmPoolTimeout' Element

void removeCmPoolTimeout()

Remove the 'cmPoolTimeout' Element

void addCmPoolMaxIdleTime()

Add a new 'cmPoolMaxIdleTime' Element

void removeCmPoolMaxIdleTime()

Remove the 'cmPoolMaxIdleTime' Element

void addCmPoolMaxRequestQueueSize()

Add a new 'cmPoolMaxRequestQueueSize' Element

void removeCmPoolMaxRequestQueueSize()

Remove the 'cmPoolMaxRequestQueueSize' Element

---

cmPoolIdMBean

cmPoolIdMBean enables you to specify the pool ID that you want to map to a physical connection.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolId

Factory Method

Created automatically

Attributes

cmPoolId

For more information about this attribute, see Table 7-2.

Operations

None

---

cmPoolMaxIdleTimeMBean

cmPoolMaxIdleTimeMBean enables you to specify the maximum idle time for a connection. When the specified time expires, the PSP SSU closes the connection.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolMaxIdleTime

Factory Method

connectionPoolConfig.addCmPoolMaxIdleTime()

Attributes

cmPoolMaxIdleTime

For more information about this attribute, see Table 7-2.

Operations

None

---

cmPoolMaxRequestQueueSizeMBean

cmPoolMaxRequestQueueSizeMBean enables you to specify the maximum size of the queue. When the maximum size is reached, the PCP SSU drops all further requests.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolMaxRequestQueueSize

Factory Method

connectionPoolConfig.addCmPoolMaxRequestQueueSize()

Attributes

cmPoolMaxRequestQueueSize

For more information about this attribute, see Table 7-2.

Operations

None

---

cmPoolMaxSizeMBean

cmPoolMaxSizeMBean enables you to specify the maximum number of connections in the pool.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolMaxSize

Factory Method

connectionPoolConfig.addCmPoolMaxSize()

Attributes

cmPoolMaxSize

For more information about this attribute, see Table 7-2.

Operations

None

---

cmPoolMinSizeMBean

cmPoolMinSizeMBean enables you to specify the minimum number of connections in the pool.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolMinSize

Factory Method

connectionPoolConfig.addCmPoolMinSize()

Attributes

cmPoolMinSize

For more information about this attribute, see Table 7-2.

Operations

None

---

cmPoolTimeoutMBean

cmPoolTimeoutMBean enables you to specify the time that the PCP SSU waits for establishing a connection.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=cmPoolTimeout

Factory Method

connectionPoolConfig.addcmPoolTimeout()

Attributes

cmPoolTimeout

For more information about this attribute, see Table 7-2.

Operations

None

---

enabledMBean

enabledMBean enables you to specify whether the connection is enabled.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=enabled

Factory Method

Created automatically

Attributes

enabled

For more information about this attribute, see Table 7-2.

Operations

None

---

hostMBean

hostMBean enables you to specify the IP address of the BRM application.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=host

Factory Method

Created automatically

Attributes

host

For more information about this attribute, see Table 7-2.

Operations

None

---

loginMBean

loginMBean enables you to specify the login that the PCP SSU uses to connect to the BRM application.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=login

Factory Method

Created automatically

Attributes

login

For more information about this attribute, see Table 7-2.

Operations

None

---

portMBean

portMBean enables you to specify the port of the BRM application.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=connectionPools,name2=connectionPoolConfig[ConnectionPoolIndex],name3=port

Factory Method

Created automatically

Attributes

port

For more information about this attribute, see Table 7-2.

Operations

None

---

opcodeRetryMBean

opcodeRetryMBean enables you to specify the number of attempts that the PCP SSU tries to execute a BRM opcode.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=opcodeRetry

Factory Method

pcpConfig.addOpcodeRetry()

Attributes

opcodeRetry

For more information about this attribute, see Table 7-1.

Operations

None

---

opcodeTimeoutMBean

opcodeTimeoutMBean enables you to specify the opcode timeout by default.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=opcodeTimeout

Factory Method

Created automatically

Attributes

opcodeTimeout

For more information about this attribute, see Table 7-1.

Operations

None

---

pcpTransactionIdleTimeoutMBean

pcpTransactionIdleTimeoutMBean enables you to specify the PCP transaction timeout.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.protocol_adapter.pcp.adapter,version=MBean_Version,name0=pcpConfig,name1=pcpTransactionIdleTimeout

Factory Method

pcpConfig.addPcpTransactionIdleTimeout()

Attributes

pcpTransactionIdleTimeout

For more information about this attribute, see Table 7-1.

Operations

None