This chapter describes how to use the Oracle Communications Billing and Revenue Management (BRM) Network Simulator to test your Telco implementation.
The Network Simulator simulates a network provisioning agent by receiving and processing XML provisioning payload files from the Provisioning DM.
Important:To use this simulator, the Provisioning DM must be running.
The Perl-based agent (agent_sim.pl) captures Service Order XML provisioning payload files from the Provisioning DM as follows:
If the $PIN_HOME environment variable is set, the Perl-based agent captures and saves the XML file in BRM_Home/apps/telco/service_orders with the name SvcOrder_EventObject_id.xml.
If the $PIN_HOME environment variable is not set, the XML file is created in the directory where the simulator is launched.
The Java-based simulator:
Processes the XML file according to command-line arguments.
Updates the service order status by calling the PCM_OP_PROV_UPDATE_SVC_ORDER opcode.
Important:Before running Network Simulator, enable provisioning. See "Enabling Wireless Provisioning".
To use the Network Simulator:
Open the CM configuration file (BRM_Home/sys/cm/pin.conf).
Uncomment the agent_return entry and set it to 1:
- fm_tcf agent_return 1
Be sure that the internal simulator is turned off by setting the simulate_agent entry to 0.
- fm_tcf simulate_agent 0
Save the file.
Restart the CM.
Start the Perl-based agent:
Perl agent_sim.pl &
Start the Provisioning DM:
Important:Always start the Perl-based agent before you start the Provisioning DM.
Create a provisioning event.
Tip:You can create a provisioning event by using Customer Center to create an account and purchase a product that requires provisioning.
(Optional) To view the XML file generated for the service order by the Provisioning DM:
Open Event Browser.
Open the service order object (/event/provisioning/service_order/telcoEventObject_ID) and note the event object ID.
Open the associated XML file, SvcOrder_EventObject_ID.xml, in the BRM_Home/apps/telco/service_orders directory by using a text editor.
To test provisioning by simulating the network, run the Java-based simulator RunSimulator. See "Running the Java-Based Simulator".
You use the Java-based simulator command RunSimulator to process the XML provisioning payload file that was created with the Perl-based agent.
If you include a parameter to change the state of a supplied service order, the status of associated service changes accordingly. For example, when a successful service order is returned, the service, product, and supplementary service (feature) status is set to Active.
To run the Java-based simulator:
Run RunSimulator at the command prompt:
RunSimulator [-d] [-s status] [-f status_flags] [-t feature_status][-m status_msg] [-x xml_file]
Status of service order.
Possible values: 0 (success; this is the default), 1 (failed)
Status flag of service order to be returned.
Supplementary service (feature) status to be returned.
XML provisioning payload file.