Using Oracle Enterprise Manager to Deploy Drivers Using the Oracle Fusion Middleware Configuration Wizard

Managing Oracle User Messaging Service 13-9 2. In Oracle Enterprise Manager, select any usermessagingserver target in the domain. 3. From the targets menu, select System MBean Browser. 4. In System MBean Browser, locate the ComponentAdministration MBean of usermessagingserver: Expand the folder com.oracle.sdp.messaging Server such as Server: soa_server1 SDPMessagingRuntime ComponentAdministration. 5. Invoke the operation listDriverInstances.

a. Click the Operations tab.

b. Click the operation listDriverInstances.

c. Click Invoke.

d. Identify and copy the name of the driver you want to unregister. for example: Farm_soa_bam_domainsoa_bam_domainsoa_ server1usermessagingdriver-email:oracle_ sdpmessagingdriver_emailEmail-Driver Figure 13–13 Listing Driver Instances

6. Click Return.

7. Invoke the operation unregisterDriverInstance with the desired driver name. a. Click the operation unregisterDriverInstance. b. Paste the driver name in the Value field for example: Farm_soa_bam_ domainsoa_bam_domainsoa_ 13-10 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite server1usermessagingdriver-email:oracle_ sdpmessagingdriver_emailEmail-Driver.

c. Click Invoke.

Figure 13–14 Unregistering a Driver Instance 8. Check the confirmation dialog for success. This completes the unregistration of the specified driver from the UMS server and it will no longer be used in future message delivery. Part V Part V Confiding SIP Infrastructure Applications This Part contains the following chapter: ■ Chapter 15, Oracle WebLogic Communication Services Base Platform Topologies 14 Configuring SIP Infrastructure Applications 14-1 14 Configuring SIP Infrastructure Applications This chapter describes Proxy Registrar and STUN Service. Topics include: ■ Section 14.1, Proxy Registrar ■ Section 14.2, STUN Service

14.1 Proxy Registrar

The Proxy Registrar is a user agent server UAS that implements the proxy and registrar functions described in RFC 3261. This SIP entity is a router of messages. The Proxy Registrars registrar function processes the REGISTER requests from User Agent clients and uses a Location Service to store a binding that is, an association between a users address of record AOR and the users SIP or SIPS URIs that are located in a CONTACT field. Upon receiving requests to the AOR, the proxy function locates the mapped URIs through a Location Service lookup and then proxies the request using the location information retrieved by this lookup. Table 14–1 describes the attributes of the Proxy Registrar. Table 14–1 Attributes of the Proxy Registrar Attributes Description CurrentRegDevices A read-only attribute that displays the number of currently registered devices. DefaultExpires Sets the expiration value for the REGISTER request if the client has not indicated a preferred value itself. The default value for this attribute is 3600 seconds. MaxExpires Sets the maximum expiration value for the REGISTER request accepted by the server. Although a client can request any expiration value in the REGISTER request, the server can set a maximum amount of time that it accepts for expiration. If the client requests a time greater than the value set for MaxEpires, then the server sets the expiration time for that particular REGISTER request to the value set for MaxExpires. The default value for this attribute is 7200 seconds.