This chapter describes how to configure the resources required to support advanced web services and SOAP over JMS in WebLogic Server Multitenant (MT) using WLST scripts. It also provides specific configurations that are required when using web services in a WebLogic Server MT environment.
This chapter includes the following sections:
WebLogic Server includes two WLST scripts that provide the ability to configure the resources required for the following JAX-WS web service features in a WebLogic Server MT environment:
wlsws-advanced-jaxws-mt-config.py—Configures advanced JAX-WS web services including asynchronous messaging, web services reliable messaging, message buffering, web services atomic transactions, and security using WS-SecureConversation.
wlsws-soapjms-mt-config.py—Configures SOAP over JMS transport.
Both scripts are located in the
/oracle_common/webservices/bin/ directory, where
oracle_home is the directory you specified as Oracle Home when you installed WebLogic Server.
To configure web service resources in a WebLogic Server MT environment:
If you have not already done so, create a domain partition. See Configuring Domain Partitions.
If you have not already done so, create a resource group in the partition. See Configuring Resource Groups.
At the domain level, create a user configuration file and an associated key file using the
storeUserConfig WLST command. See "storeUserConfig" in WLST Command Reference for WebLogic Server.
Execute one or both of the WLST scripts from the
/bin/java directory. Note that you must include the location of the
weblogic.jar file in the classpath.
For example, to configure the resources required for the WebLogic Server MT advanced web services for JAX-WS, use the following command:
JAVA_HOME/bin/java -classpath weblogic.jar_location weblogic.WLST ./wlsws-advanced-jaxws-mt-config.py -myUserConfigFile userConfigFile -myUserKeyFile userKeyFile -myURL AdminServer_t3_url -partitionName partitionName -rgName resourceGroupName -isCluster true_or_false -middlewareHome middlewareHomeDir
To configure the resources required in WebLogic Server MT for SOAP over JMS transport, use the following command:
JAVA_HOME/bin/java -classpath weblogic.jar_location weblogic.WLST ./wlsws-soapjms-mt-config.py -myUserConfigFile userConfigFile -myUserKeyFile userKeyFile -myURL AdminServer_t3_url -partitionName partitionName -rgName resourceGroupName -isCluster true_or_false -middlewareHome middlewareHomeDir
Both scripts require the command options described in Table 26-1.
Name of the file you specified for the
Name of the file you specified for the
T3 protocol URL for the Administration Server for the partition, for example
Name of the partition in which the resources are being configured.
Name of the resource group in the partition.
Argument that indicates if the partition is in a cluster. Valid values are:
Location of the directory that you specified as the Oracle Home directory when you installed WebLogic Server.
SOAP over JMS supports both queues and topics as the JMS destination type. The type that you use is determined by the application.
When using a uniform distributed topic as the request destination for SOAP over JMS in a WebLogic Server MT environment, you must use a partitioned uniform distributed topic.
In WebLogic JMS, distributed topics can be configured as replicated distributed topics or partitioned distributed topics. While replicated distributed topics work with
topicMessageDistributionMode settings of
One-Copy-Per-Application, partitioned distributed topics only work with
To configure a partitioned uniform distributed topic for SOAP over JMS in WebLogic Server MT, configure the
@JMSTransportService annotation as follows:
topicMessageDistributionMode configuration property on the
activationConfig property to
Compatibility value is not supported for partitioned distribution topics.
@JMSTransportService(targetService="poNotifyService" , destinationName="com.oracle.webservices.jms.SoapJmsRequestTopic" , destinationType=JMSDestinationType.TOPIC , activationConfig = "topicMessagesDistributionMode=One-Copy-Per-Application" , jndiURL = "t3://@wls-server@"
For more information, see "Using SOAP Over JMS Transport" in Developing JAX-WS Web Services for Oracle WebLogic Server.
Note:You must configure the JMS topic before deploying the SOAP over JMS application using the partitioned distributed topic. For more information, see "Configuring Partitioned Distributed Topics" in Administering JMS Resources for Oracle WebLogic Server.
See the following sections for additional information related to advanced web services:
"storeUserConfig" in WLST Command Reference for WebLogic Server
"Creating and Configuring Servlets" in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server