# System Administrator’s Guide

# Managing and Configuring WAP Push Communication Services

The following section describes configuration and maintenance attributes and operations for the Extended Web Services WAP Push communication service. It also provides a workflow for the configuration:

- Extended Web Services WAP Push/PAP

- Configuration Workflow for Extended Web Services WAP Push/PAP
- Management for Extended Web Services WAP Push/PAP
- Provisioning for Extended Web Services WAP Push/PAP
- Reference: Attributes and Operations for WAP Push/PAP

## Extended Web Services WAP Push/PAP

All WAP Push related operations are handed off to network nodes that accept and forward WAP Push messages to end user terminals via a Push Proxy Gateway (PPG).

To see a | Refer to
--- | ---
Detailed list of necessary for managing and configuring the plug-in instance | Properties for Extended Web Services WAP Push/PAP
Configuration workflow | Configuration Workflow for Extended Web Services WAP Push/PAP
List of operations and attributes related to management and provisioning | Management for Extended Web Services WAP Push/PAP Provisioning for Extended Web Services WAP Push/PAP
Reference of management attributes and operations | Reference: Attributes and Operations for WAP Push/PAP

### Properties for Extended Web Services WAP Push/PAP

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.pushmessage.pap.management.PushMessagePAPMBean
Network protocol plug-in service ID | Plugin_ews_push_message_pap
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 wapuser
North interface | com.bea.wlcp.wlng.ews.plugin.PushMessagePlugin com.bea.wlcp.wlng.ews.callback.PushMessageNotificationCallback
Service type | PushMessage
Exposes to the service communication layer a Java representation of: | Extended Web Services WAP Push
Interfaces with the network nodes using: | Push Access Protocol (PAP), 2.0. WAP-247-PAP-20010429-a
Deployment artifacts NT EAR wlng_nt_push_message_ews.ear | ews_push_message_service.jar, Plugin_ews_push_message_pap.jar, and ews_push_message_pap.war
AT EAR: Normal wlng_at_push_message_ews.ear | ews_push_message.war, ews_push_message_callback.jar, and rest_push_message.war
AT EAR: SOAP Only wlng_at_push_message_ews_soap.ear | ews_push_message.war and ews_push_message_callback.jar

### Configuration Workflow for Extended Web Services WAP Push/PAP

Below is an outline for configuring an Extended Web Service WAP Push/PAP network protocol plug-in instance:

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 Extended Web Services WAP Push/PAP.
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. Define the characteristics of the PPG server to connect to by specifying:

Attribute: PPGNotificationURL

Attribute: PPGURL

4. Specify heartbeat behavior, see Configuring Heartbeats
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 Extended Web Services WAP Push/PAP.
6. If desired, create and load a node SLA, see:

Defining Global Node and Service Provider Group Node SLAs

Managing Application SLAs

Move on to the provisioning of service provider accounts and application accounts.

### Management for Extended Web Services WAP Push/PAP

No specific management operations.

### Provisioning for Extended Web Services WAP Push/PAP

No specific provisioning operations.

### Reference: Attributes and Operations for WAP Push/PAP

Below is a list of attributes for configuration and maintenance:

- Attribute: PPGNotificationURL
- Attribute: PPGURL

### Attribute: PPGNotificationURL

Scope: Server

Unit: n/a

Format: String

Specifies the URL of the plug-in instance. Used by the Push Proxy Gateway (PPG) to send notifications of results to the plug-in instance.

### Attribute: PPGURL

Scope: Cluster

Unit: n/a

Format: String

Specifies the URL of the Push Proxy Gateway (PPG) the plug-in instance uses.