Running Methods for PCMM Services (SRC CLI)

To run a method for the PCMM Web service interface:

• Run the test dsa pcmm-service command.

  user@host> test dsa pcmm-service (commit-resources | release-resources | query-contexts | query-available-services)

  where:

  • commit-resources—Specifies the resources that are being requested in the CommitResource message.
  • release-resources—Specifies the resources that are being requested to be released in the ReleaseResources message.
  • query-contexts—Searches for the context ID and context status for a subscriber.
  • query-available-services—Searches for the services that are available to the calling application.

• Testing Resource Requests (SRC CLI)
• Testing Resource Release Requests (SRC CLI)
• Testing Queries for Subscriber Contexts (SRC CLI)
• Testing Queries for Available Services (SRC CLI)

Testing Resource Requests (SRC CLI)

Use the following command to test the method that specifies the resources that are being requested in the CommitResource message:

To test the method:

1. Issue the test dsa pcmm-service commit-resources command.
2. To specify the name of the SRC service, use the service-name option.
3. (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
4. (Optional) To specify the subscriber’s Uniform Resource Identifier (URI), use the subscriber-uri option.
5. (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
6. (Optional) To specify a limit on the lifetime of a context, use the time-usage-limit option. An application server may specify multiple time usage limits to request different limits in the upstream and downstream directions. If the application server does not specify a time usage limit, the application manager determines the time usage limit.
7. (Optional) To specify the object that identifies the traffic flow for which the application server is requesting services, use the classifier option.
8. (Optional) To specify information about the bandwidth and QoS characteristics desired for a request, use the traffic-profile option. You express the traffic profile by configuring the SRC policies with FlowSpec, service class name, or DOCSIS actions.
9. (Optional) To specify a FlowSpec action, use the flow-spec option.
10. (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
11. (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.

Testing Resource Release Requests (SRC CLI)

Use the following command to test the method that specifies the resources that are being requested to be released in the ReleaseResources message:

To test the method:

1. Issue the test dsa pcmm-service release-resources command.
2. (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
3. (Optional) To specify the subscriber’s Uniform Resource Identifier (URI), use the subscriber-uri option.
4. (Optional) To specify the name of the SRC service, use the service-name option.
5. (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
6. (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
7. (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.

Testing Queries for Subscriber Contexts (SRC CLI)

Use the following command to test the method that searches for the context ID and context status for a subscriber:

To test the method:

1. Issue the test dsa pcmm-service query-contexts command.
2. (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
3. (Optional) To specify the subscriber’s URI, use the subscriber-uri option.
4. (Optional) To specify the name of the SRC service, use the service-name option.
5. (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
6. (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
7. (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.

Testing Queries for Available Services (SRC CLI)

Use the following command to test the method that searches for the services that are available to the calling application:

To test the method:

1. Issue the test dsa pcmm-service query-available-services command.
2. (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
3. (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.

Related Topics

• Testing the Web Application Gateway Client
• Sample Data for Dynamic Service Activator
• Running Methods and Scripts for Dynamic Service Activator Services (SRC CLI)
• Configuring the Test Environment for PCMM Services

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.