Configuring the Host WebLogic Server Instance for the JMS Transport Web Service
8.4 Configuring the Host WebLogic Server Instance for the JMS Transport Web Service
Configuring the WebLogic Server instance on which the JMS transport Web service is deployed involves configuring JMS resources, such as JMS servers and modules, that are used internally by the Web services runtime. You can configure these resources manually or you can use the Configuration Wizard to extend the WebLogic Server domain using a Web services-specific extension template. Using the Configuration Wizard greatly simplifies the required configuration steps; for details, see Configuring Your Domain For Web Services Features in Getting Started With JAX-RPC Web Services for Oracle WebLogic Server. If you prefer to configure the resources manually, perform the following steps. Notes: Alternatively, you can use WLST to configure the resources. For information about using WLST to extend the domain, see Configuring Existing Domains in Oracle WebLogic Scripting Tool. A domain that does not contain Web Services resources will still boot and operate correctly for non-Web services scenarios, and any Web Services scenario that does not involve asynchronous request and response. You will, however, see INFO messages in the server log indicating that asynchronous resources have not been configured and that the asynchronous response service for Web services has not been completely deployed. Table 8–3 Steps to Configure Host WebLogic Server Instance Manually for the JMS Transport Web Service Step Description 1 Invoke the Administration Console for the domain that contains the host WebLogic Server instance. To invoke the Administration Console in your browser, enter the following URL: http:host:portconsole where ■ host refers to the computer on which the Administration Server is running. ■ port refers to the port number where the Administration Server is listening for connection requests. The default port number for the Administration server is 7001. See Invoking the Administration Console in Getting Started With JAX-RPC Web Services for Oracle WebLogic Server. 8-6 Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server8.5 Using the WLJmsTransport JWS Annotation
Parts
» Oracle Fusion Middleware Online Documentation Library
» Overview of the Asynchronous Request-Response Feature
» Using Asynchronous Request-Response: Main Steps
» Configuring the Host WebLogic Server Instance for the Asynchronous Web Service
» Example of a Synchronous Invoke
» Configuring the Source WebLogic Server Instance
» Creating a Custom WS-Policy File Using WS-ReliableMessaging Policy Assertions Version 1.1
» Using Multiple Policy Alternatives
» Programming Guidelines for the JWS File That Invokes a Reliable Web Service
» Overview of Conversational Web Services
» Creating a Conversational Web Service: Main Steps
» Programming Guidelines for the Conversational JWS File
» Programming Guidelines for the JWS File That Invokes a Conversational Web Service
» Updating a Stand-Alone Java Client to Invoke a Conversational Web Service
» ConversationService.java File Example Conversational Web Service .NET Client
» Service.cs File Example Conversational Web Service .NET Client
» build.xml File Example Conversational Web Service .NET Client
» Configuring the Host WebLogic Server Instance for the Buffered Web Service
» Programming Guidelines for the Buffered JWS File
» Using the Asynchronous Features Together
» Example of a JWS File That Implements a Reliable Conversational Web Service
» Overview of Callbacks Callback Implementation Overview and Terminology
» Programming Callbacks: Main Steps Programming Guidelines for Target Web Service
» Programming Guidelines for the Callback Client Web Service
» Programming Guidelines for the Callback Interface
» Updating the build.xml File for the Client Web Service
» Overview of Using JMS Transport
» Using JMS Transport Starting From Java: Main Steps
» Using JMS Transport Starting From WSDL: Main Steps
» Configuring the Host WebLogic Server Instance for the JMS Transport Web Service
» Using the WLJmsTransport JWS Annotation
» Using the WLJmsTransport Child Element of the jwsc Ant Task Updating the WSDL to Use JMS Transport
» Overriding the Default Service Address URL
» Using JMS BytesMessage Rather Than the Default TextMessage Disabling HTTP Access to the WSDL File
» Overview of SOAP Message Handlers
» Adding SOAP Message Handlers to a Web Service: Main Steps
» Designing the SOAP Message Handlers and Handler Chains
» Implementing the Handler.handleResponse Method
» javax.jws.HandlerChain Configuring Handlers in the JWS File
» javax.jws.soap.SOAPMessageHandlers
» Creating the Handler Chain Configuration File
» Compiling and Rebuilding the Web Service
» Using Client-Side SOAP Message Handlers: Main Steps
» Example of a Client-Side Handler Class Creating the Client-Side SOAP Handler Configuration File
» Database Call-out Overview of Database Web Services
» SQL to XML Type Mappings for Web Service Call-Ins
» UDDI and Web Services UDDI and Business Registry
» Configuring an External LDAP Server
» Description of Properties in the uddi.properties File
Show more