5 Managing and Configuring SOA Facades

This chapter describes how to configure the Oracle Communications Services Gatekeeper Service Oriented Architecture (SOA) Facades in Oracle Service Bus (OSB).

Introduction

The Oracle SOA Suite is an Oracle Fusion Middleware Component that allows you to assemble multiple services into SOA composite applications for service consumers to use. You administer the SOA Suite using the Oracle Enterprise Manager Fusion Middleware Control Console. The SOA Suite relies on another Oracle Middleware Component, the Oracle Service Bus (OSB). It is the OSB that you must install and configure with Service Gatekeeper so that it communicates with the SOA Facades.

To provide SOA support, Services Gatekeeper domains must have each AT server collocated with OSB. Figure 5-1 shows a Services Gatekeeper domain with the OSB and AT collocated on the same server.

Figure 5-1 Services Gatekeeper Domain with SOA Support

The OSB then interfaces with the Services Gatekeeper NT layer. Figure 5-2 shows how an application request flows through the OSB to the AT tier and finally to the NT tier. Return communication flows back in reverse order.

Figure 5-2 Services Gatekeeper-SOA Communication Order

During installation, you configure OSB using the SOA domain configuration template provided with Services Gatekeeper, and manage SOA Facades using the OSB Administration Console.

The OSB administration console is located at http://admin_server_IP_addr/sbconsole. For each communication service there is a set of business services and proxy services, one for each SOAP interface.

You do not need to configure the SOA Facades, but both the business services and the proxy services are configured in the same manner as other OSB projects. You load SOA Facades projects using the Service Bus Console.

Upgrading SOA Facade Projects From Previous Release

You need to upgrade any existing SOA facade projects created in previous releases of Service Gatekeeper to this release. To do this you import these SOA facade projects into Services Gatekeeper using System Administration console, and then export them again using these steps:

(Optional) Save copies of the old SOA facade projects .jar files a neutral location.
Follows the steps in Loading SOA Facade Projects to load your existing projects into Services Gatekeeper.
Under System Administration, click on Export Resources.
Select all SOA projects.
Click Export.

Export the files to their original locations, overwriting the original files with the updated versions.

You can now use your SOA facade projects with Services Gatekeeper 5.0.

Loading SOA Facade Projects

This section describes how to load the SOA Facade projects.

The SOA Service Facades are not loaded by default. Load the projects for the Communication Services that are to be used using the instruction below.

See "Available SOA Facades" for a list of available SOA Facades and the deployment artifacts for them.

In the Service Bus administration console, click on System Administration.
Under System Administration, click on Import Resources.
Click the Browse button next to the File Name entry field.
Browse to the directory domain_home/soa and select the .jar file, according to Table 5-1.
In the Import Resources- Project JAR File screen, click the Import button.

Note:
In the Change Center, click the Activate button.

Available SOA Facades

Table 5-1 lists the SOA Facades for Services Gatekeeper. The files are located in domain_home/soa.

Table 5-1 SOA Facade projects and services

Service Facade	Project	File
Not applicable	soa_common	File: sb_common.jar Business Service: Not applicable Proxy Service: Not applicable Type: Use for both application-initiated and network-triggered requests.
Session Manager	soa_session	File: sb_session.jar Business Service: SessionManager_BS Proxy Service: SessionManager_PS Type: Use for application-initiated requests.
Parlay X 2.1 Audio Call	soa_audio_call_pz21	File: sb_ac_px21.jar Business Service: AudioCall_BS Proxy Service: AudioCall_PS Type: Use for application-initiated requests.
Parlay X 3.0 Audio Call	soa_audio_call_px30	File: sb_ac_px30.jar Business Service: AudioCallCaptureMedia_BS Business Service: AudioCallPlayMedia_BS Proxy Service: AudioCallCaptureMedia_PS Proxy Service: AudioCallPlayMedia_PS Type: Use for application-initiated requests.
Parlay X 2.1 Call Notification	soa_call_notification_px21	File: sb_cn_px21.jar Business Service: CallDirection_BS Business Service: CallDirectionManager_BS Business Service: CallNotification_BS Business Service: CallNotificationManager_BS Proxy Service: CallDirection_PS Proxy Service: CallDirectionManager_PS Proxy Service: CallNotification_PS Proxy Service: CallNotificationManager_PS Type: Use for network-triggered requests.
Parlay X 3.0 Call Notification	soa_call_notification_px30	File: sb_cn_px30.jar Business Service: CallDirection_BS Business Service: CallDirectionManager_BS Business Service: CallNotification_BS Business Service: CallNotificationManager_BS Proxy Service: CallDirection_PS Proxy Service: CallDirectionManager_PS Proxy Service: CallNotification_PS Proxy Service: CallNotificationManager_PS Type: Use for network-triggered requests.
Parlay X 2.1 Multimedia Messaging	soa_mms_px21	File: sb_mms_px21.jar Business Service: MessageNotification_BS Business Service: MessageNotificationManager_BS Business Service: ReceiveMessage_BS Business Service: SendMessage_BS Proxy Service: MessageNotification_PS Proxy Service: MessageNotificationManager_PS Proxy Service: ReceiveMessage_PS Proxy Service: SendMessage_PS Type: Use for both application-initiated and network-triggered requests.
Parlay X 3.0 Payment	soa_payment_px30	File: sb_payment_px30.jar Business Service: AmountCharging_BS Business Service: ReserveAmountCharging_BS Proxy Service: AmountCharging_PS Proxy Service: ReserveAmountCharging_PS Type: Use for application-initiated requests.
Parlay X 2.1 Presence	soa_presence_px21	File: sb_presence_px21.jar Business Service: PresenceConsumer_BS Business Service: PresenceNotification_BS Business Service: PresenceSupplier_BS Proxy Service: PresenceConsumer_PS Proxy Service: PresenceNotification_PS Proxy Service: PresenceSupplier_PS Type: Use for both application-initiated and network-triggered requests.
Parlay X 2.1 Short Messaging	soa_sms_px21	File: sb_sms_px21.jar Business Service: ReceiveSms_BS Business Service: SendSms_BS Business Service: SmsNotification_BS Business Service: SmsNotificationManager_BS Proxy Service: ReceiveSms_PS Proxy Service: SendSms_PS Proxy Service: SmsNotification_PS Proxy Service: SmsNotificationManager_PS Type: Use for both application-initiated and network-triggered requests.
Extended Web Services Subscriber Profile	soa_subscriber_ews	File: sb_subscriber_ews.jar Business Service: SubscriberProfile_BS Proxy Service: SubscriberProfile_PS Type: Use for application-initiated requests.
Parlay X 2.1 Third Party Call	soa_third_party_call_px21	File: sb_tpc_px21.jar Business Service: ThirdPartyCall_BS Proxy Service: ThirdPartyCall_PS Type: Use for application-initiated requests.
Parlay X 3.0 Third Party Call	soa_third_party_call_px30	File: sb_tpc_px30.jar Business Service: ThirdPartyCall_BS Proxy Service: ThirdPartyCall_PS Type: Use for application-initiated requests.
Parlay X 2.1 Terminal Status	soa_ts_px21	File: sb_ts_px21.jar Business Service: TerminalStatusNotificationManager_BS Proxy Service: TerminalStatusNotificationManager_PS Type: Use for both application-initiated and network-triggered requests.
Parlay X 2.1 Terminal Location	soa_tl_px21	File: sb_tl_px21.jar Business Service: TerminalLocation_BS Business Service: TerminalLocationNotification_BS Business Service: TerminalLocationNotificationManager_BS Proxy Service: TerminalLocation_PS Proxy Service: TerminalLocationNotification_PS Proxy Service: TerminalLocationNotificationManager_PS Type: Use for both application-initiated and network-triggered requests.
Parlay X 3.0 Device Capabilities and Configuration	soa_device_capabilities_px30	File: sb_dc_px_30.jar Business Service: DeviceCapabilities_BS Proxy Service: DeviceCapabilities_PS Type: Use for application-initiated requests.
Callable Policy	soa_callable_policy	File: sb_session.jar, sb_callable_policy.jar Business Service: Policy_BS Proxy Service: Policy_PS Type: Use for application-initiated requests.
Extended Web Services WAP Push	soa_wap_ews	File: sb_wap_ews.jar Business Service: PushMessage_BS Business Service: PushMessageNotification_BS Proxy Service: PushMessage_PS Proxy Service: PushMessageNotification_PS Type: Use for application-initiated requests.
Extended Web Services Binary SMS	soa_sms_ews	File: sb_sms_ews.jar Business Service: BinarySms_BS Business Service: BinarySmsNotification_BS Business Service: BinarySmsNotificationManager_BS Proxy Service: BinarySms_PS Proxy Service: BinarySmsNotification_PS Proxy Service: BinarySmsNotificationManager_PS Type: Use for both application-initiated and network-triggered requests.