Sonic Alert B31540-02 manual Configuring the Middleware

Sl.	Event Name	Event Display Name	Description
No
10	oracle.apps.ar.hz.CustomerProfile.	Customer Profile	Triggered when
	update	Update	Customer Profile
			details are updated.
11	oracle.apps.ar.hz.ContactPoint.up	Contact Points Update	Triggered when
	date		Contact Point details
			are updated.

Configuring the Middleware

Oracle TBI uses generic XML gateway compatible Advance Queues (AQ) for all outgoing and incoming messages. They are:

1.WF_JMS_IN: This inbound queue is used for all inbound messages that are sent to TBI. Once the billing application receives the message, it sends a Confirmation Business Object Document (CBOD) with appropriate status to the Middleware, which queues it onto the WF_JMS_IN. The Workflow Agent configured on the WF_JMS_IN queue picks up the message and calls the workflow handlers to process the message.

2.WF_JMS_OUT: This is the JMS Outbound queue that processes outbound transactions. The Account XML message generated in JMS Format is published to the JMS Outbound queue (WF_JMS_OUT). The Collaboration history is updated to reflect the account message publish status.

Note: If Oracle Applications Interconnect (OAI 9.0.4) is used as the middleware, refer Appendix A for details on configuring OAI 9.0.4. If a non-OAI middleware is used, refer to the respective documentation for the configuration details.

Implementation Tasks for Oracle Telecommunications Billing Integrator 3-23