# System Administrator’s Guide

# Managing and Configuring Payment Communication Services

The following section describes configuration and maintenance attributes and operations for the communication services that expose Parlay X 3.0 Payment Web Services interfaces. The sections also provide a workflow for the configuration:

- Parlay X 3.0 Payment /Diameter

- Properties for Parlay X 3.0 Payment/Diameter
- Configuration Workflow for Parlay X 3.0 Payment/Diameter
- Provisioning Workflow for Parlay X 3.0 Payment/Diameter
- Reference: Attributes and Operations for Parlay X 3.0 Payment/Diameter

## Parlay X 3.0 Payment /Diameter

This section contains a description of the configuration attributes and operations available for Parlay X 3.0 Payment/Diameter network protocol plug-in instances.

To see a | Refer to
--- | ---
Detailed list of necessary for managing and configuring a plug-in instance | Properties for Parlay X 3.0 Payment/Diameter
Configuration workflow | Configuration Workflow for Parlay X 3.0 Payment/Diameter
List of operations and attributes related to management and provisioning | Provisioning Workflow for Parlay X 3.0 Payment/Diameter
Reference of management attributes and operations | Reference: Attributes and Operations for Parlay X 3.0 Payment/Diameter

### Properties for Parlay X 3.0 Payment/Diameter

Property | Description
--- | ---
Managed object in Administration Console | <domain name>OCSG<server name>Communication Services<plug-in instance ID>
MBean | Domain=com.bea.wlcp.wlng Name=wlng_nt InstanceName is same as plug-in instance ID Type=com.bea.wlcp.wlng.plugin.payment.diameter.management.PaymentMBean
Network protocol plug-in service ID | Plugin_px30_payment_diameter
Network protocol plug-in instance ID | The ID is given when the plug-in instance is created, see Managing and Configuring the Plug-in Manager.
Supported Address Scheme | tel
North interfaces | com.bea.wlcp.wlng.px30.plugin.AmountChargingPlugin com.bea.wlcp.wlng.px30.plugin.ReserveAmountChargingPlugin
Service type | Payment
Exposes to the service communication layer a Java representation of: | Parlay X 3.0 Part 6: Payment
Interfaces with the network nodes using: | Diameter RFC3588 and RFC 4006
Deployment artifacts NT EAR wlng_nt_payment_px30.ear | Plugin_px30_payment_diameter.jar and px30_payment_service.jar
AT EAR: Normal wlng_at_payment_px30.ear | rest_payment.war and px30_payment.war
AT EAR: SOAP Only wlng_at_payment_px30_soap.ear | px30_payment.war

### Configuration Workflow for Parlay X 3.0 Payment/Diameter

Below is an outline for configuring the plug-in using the Oracle Communications Services Gatekeeper Management Console:

1. Create one or more instances of the plug-in service: see Managing and Configuring the Plug-in Manager. Use the plug-in service ID as detailed in Properties for Parlay X 3.0 Payment/Diameter.
2. Using the Management Console or an MBean browser, select the MBean for the plug-in instance. The MBean display name is the same as the plug-in instance ID given when the plug-in instance was created.
3. Configure the behavior of the plug-in instance:

- Attribute: Connected
- Attribute: DestinationHost
- Attribute: DestinationPort
- Attribute: DestinationRealm
- Attribute: OriginHost
- Attribute: OriginPort
- Attribute: OriginRealm

4. Use Operation: connect to connect to the Diameter server.
5. Set up the routing rules to the plug-in instance: see Configuring the Plug-in Manager. Use the plug-in instance ID and address schemes detailed in Properties for Parlay X 3.0 Payment/Diameter.
6. If desired, create and load a node SLA, see:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

Continue with the provisioning of service provider accounts and application accounts.

Management of Parlay X 3.0 Payment/Diameter

The Parlay X 3.0 Payment/Diameter plug-in instance can be explicitly connected to the Diameter server. It does not connect to the server by default. The service has a connection status that will be preserved after service redeployment and server restart.

Use:

- Operation: connect
- Operation: disconnect

Use Operation: connect after any changes to the configuration attributes. Changes does not take affect until this operation is invoked.

### Provisioning Workflow for Parlay X 3.0 Payment/Diameter

No provisioning operations.

### Reference: Attributes and Operations for Parlay X 3.0 Payment/Diameter

Managed object: Communication Services-><plug-in instance ID>

MBean: com.bea.wlcp.wlng.plugin.payment.diameter.management.PaymentMBean

Below is a list of attributes and operations for configuration and maintenance:

- Attribute: Connected
- Attribute: DestinationHost
- Attribute: DestinationPort
- Attribute: DestinationRealm
- Attribute: OriginPort
- Attribute: OriginHost
- Attribute: OriginRealm
- Operation: connect
- Operation: disconnect

### Attribute: Connected (r)

Read-only.

Scope: Server

Format: Boolean

Unit: n/a

Displays the status of the connection to the Diameter server.

Displays:

- `true`, if connected.

`false`, if not connected.

### Attribute: Connected

Scope: Cluster

Unit: n/a

Format: String

Specifies the value of the Destination-Host AVP in Diameter requests.

Example:

host.destination.com

### Attribute: DestinationHost

Scope: Cluster

Unit: n/a

Format: String

Specifies the host name of the Diameter server to connect to.

Example:

host.destination.com

### Attribute: DestinationPort

Scope: Cluster

Unit: n/a

Format: int

Specifies the port on the Diameter server to connect to.

Example:

3588

### Attribute: DestinationRealm

Scope: Cluster

Unit: n/a

Format: String

Specifies the Destination-Realm AVP in Diameter requests.

Example:

destination.com

### Attribute: OriginHost

Scope: Cluster

Unit: n/a

Format: String

Specifies the Origin-Host AVP in Diameter requests.

Example:

host.oracle.com

### Attribute: OriginPort

Scope: Cluster

Unit: n/a

Format: int

Specifies the local originator port to be used for the connection to the Diameter server.

Example:

7002

### Attribute: OriginRealm

Scope: Cluster

Unit: n/a

Format: String

Specifies the Origin-Realm AVP in Diameter requests.

Example:

oracle.com

### Operation: connect

Scope: Cluster

Connects to the Diameter server.

Once connected, the service will try to reconnect to the Diameter server if the server is restarted or the plug-in is redeployed.

Signature:

    connect()

Table 25-1 connect
connect
Parameter | Description
--- | ---
- | -

### Operation: disconnect

Scope: Cluster

Disconnects from the Diameter server.

Once disconnected, the plug-in will not try to reconnect to the DAMETER server if the server is restarted or the plug-in is redeployed.

Signature:

    disconnect()

Table 25-2 disconnect
disconnect
Parameter | Description
--- | ---
- | -