Using WebLogic Server Administration Console

Managing Oracle User Messaging Service 13-5

13.1.2 Using Oracle Enterprise Manager to Deploy Drivers

Follow these steps to deploy drivers using Oracle Enterprise Manager.

1. Retrieve a deployment template for example: ORACLE_

HOMEcommunicationsplans

2. Copy the plan to a location of your choice to the same directory or any other

directory.

3. Edit the plan:

Replace DriverDeploymentName with whichever name you want to use ensure you replace all instances of the name. Replace DriverShortName with any name you like.

4. Start Oracle Enterprise Manager.

5. Enter the location of the .ear file

Figure 13–9 .

6. Enter the location of the Deployment Plan

Figure 13–9 . Figure 13–9 Deploying UMS Drivers using Oracle Enterprise Manager The Select Target screen appears. 13-6 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite Figure 13–10 Select Target screen

7. Select the SOA target.

8. Enter an application name in the Application Attributes screen. The application

name must exactly match the string used for DriverDeploymentName in Step 3 above which is provided in the Deployment Plan. If it does not, the deployment and activation will fail. The Deployment Setting screen appears. Figure 13–11 Deployment Settings screen

9. Click Deploy. The Deployment Completed screen appears.

Managing Oracle User Messaging Service 13-7 Figure 13–12 Deployment Completed screen

10. To see the result driver deployed, start the SOA Server.

13.1.3 Using WLST Commands

You can deploy drivers using the WLST command deployUserMessagingDriver.

13.1.3.1 deployUserMessagingDriver

Command Category: UMS Use with WLST: Online

13.1.3.1.1 Description

deployUserMessagingDriver is used to deploy additional instances of user messaging drivers. Specify a base driver type for example: email, xmpp, voicexml, and others and a short name for the new driver deployment. The string usermessagingdriver- will be prepended to the specified application name. Any valid parameters for the deploy command can be specified, and will be passed through when the driver is deployed. 13.1.3.1.2 Syntax deployUserMessagingDriverbaseDriver, appName, [targets], [stageMode], [options] Argument Definition baseDriver Specifies the base messaging driver type. Must be a known driver type, such as email, proxy, smpp, voicexml, or xmpp. appName A short descriptive name for the new deployment. The specified value will be prepended with the string usermessagingdriver- 13-8 Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite

13.1.3.1.3 Examples To deploy a second instance of an email driver with name

myEmail. wls:base_domainserverConfig deployUserMessagingDriverbaseDriver=email, appName=myEmail To deploy a second instance of an email driver, specifying deployment targets. wls:base_domainserverConfig deployUserMessagingDriverbaseDriver=email, appName=email2, targets=server1,server2

13.1.4 Using the Oracle Fusion Middleware Configuration Wizard

To install the SMPP, XMPP and VoiceXML drivers, extend the domain using the extension template available at ORACLE_ HOMEcommontemplatesapplicationsoracle.ums.drivers_template_ 11.1.1.jar. To extend a domain using Oracle Fusion Middleware Configuration Wizard: 1. Launch Oracle Fusion Middleware Configuration Wizard ORACLE_ HOMEcommonbinconfig.sh or ORACLE_ HOME\common\bin\config.cmd. 2. Select the Extend an existing WebLogic domain option. 3. Select the desired domain directory containing UMS. 4. Select the Extend my domain using an existing extension template option.

5. Click Browse, and navigate to ORACLE_

HOMEcommontemplatesapplications 6. Select oracle.ums.drivers_template_11.1.1.jar 7. Complete the remaining steps of the Oracle Fusion Middleware Configuration Wizard, and remember to target the required drivers to the desired WebLogic servers andor clusters. 8. Restart the appropriate WebLogic servers.

13.2 Undeploying and Unregistering Drivers

Since Messaging Drivers are standard JEE applications, they can be undeployed from the Oracle WebLogic Server using standard Oracle WebLogic tools such as the Admin Console or WLST. However, since the UMS server keeps track of the messaging drivers that have been registered with it in a persistent store database, this registration must be cleaned in a separate step using a runtime MBean exposed by the UMS server. The procedure to do this from Oracle Enterprise Manager is as follows: 1. Ensure the UMS server is available. targets stageMode options Optional. Additional arguments that are valid for the deploy command can be specified and will be passed through when the new driver is deployed. Argument Definition 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_