The following sections describe how to perform common web services administration tasks using WLST.
To view all the current web services in a domain:
For more information about the listWSMPolicySubjects
and listWebServices
commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To view the web services in your application:
For details about the listWebServices
command, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To view the details for a web service endpoint (port):
For more information about these WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
Use the following procedure to view the web service clients using WLST commands:
Note:
The procedures described in this section apply to non-SOA Oracle Infrastructure web services and providers only.
Oracle Infrastructure web service providers implement the java.xml.ws.Provider
interface. On the Web Service Endpoint page, they display the Implementation Class and provide a subset of configuration properties.
You configure the web service endpoint using WLST by attaching one of the configuration policies defined in "Configuration Policies" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
The following sections describe how to perform common web services configuration tasks using WLST.
Configuring the JMS System User for Asynchronous Web Services Using WLST
Enabling or Disabling Public Access to the Web Service WSDL Document Using WLST
Enabling or Disabling the Processing of SOAP Requests Using WLST
Enabling or Disabling Non-SOAP XML Message Processing Using WLST
Overview of Enabling or Disabling the Web Services Test Client Using WLST
Enabling or Disabling MTOM-encoded SOAP Fault Messages Using WLST
To configure web services addressing using WLST:
To disable the addressing policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an addressing policy configured at a higher scope, attach the oracle/no_addressing_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_addressing_policy")
Policy reference "oracle/no_addressing_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure asynchronous web services:
To disable the asynchronous policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an asynchronous policy configured at a higher scope, attach the oracle/no_async_web_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_async_web_service_policy")
Policy reference "oracle/no_async_web_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure the JMS system user for asynchronous web services:
To disable the asynchronous policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an asynchronous policy configured at a higher scope, attach the oracle/no_async_web_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_async_web_service_policy")
Policy reference "oracle/no_async_web_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure web services reliable messaging using WLST:
To disable the web service reliable messaging policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a reliable messaging policy configured at a higher scope, attach the oracle/no_reliable_messaging_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_reliable_messaging_policy")
Policy reference "oracle/no_reliable_messaging_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure web services atomic transactions:
To disable the web service atomic transaction policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an atomic transaction policy configured at a higher scope, attach the oracle/no_atomic_transaction_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_atomic_transaction_policy")
Policy reference "oracle/no_atomic_transaction_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure MTOM on the web service using WLST:
To disable the web service atomic transaction policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an MTOM policy configured at a higher scope, attach the oracle/no_mtom_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_mtom_policy")
Policy reference "oracle/no_mtom_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure Fast Infoset on the web service or client using WLST:
To disable the web service Fast Infoset policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a Fast Infoset policy configured at a higher scope, attach the oracle/no_fast_infoset_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_fast_infoset_service_policy")
Policy reference "oracle/no_fast_infoset_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure SOAP over JMS transport on the web service or client using WLST:
To disable the SOAP over JMS transport policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a SOAP over JMS transport policy configured at a higher scope, attach the oracle/no_jms_transport_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_jms_transport_service_policy")
Policy reference "oracle/no_jms_transport_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To configure the persistence using WLST:
To disable the persistence policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a persistence policy configured at a higher scope, attach the oracle/no_persistent_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_persistent_policy")
Policy reference "oracle/no_persistent_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
When a web service application is deployed, the web service endpoint is enabled by default if no errors are encountered. If there are errors, the web service application is deployed, but the web service endpoint is not enabled.
You may need to temporarily make a web service unavailable by disabling the web service. For example, you may need to correct an invalid policy reference. When you disable a web service, requests to the web service will fail. To disable a web service, you must make the endpoint on which the web service receives requests unavailable.
To enable a web service endpoint using WLST:
To disable the web service access policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a web service access policy configured at a higher scope, attach the oracle/no_pox_http_binding_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_request_processing_service_policy")
Policy reference "oracle/no_request_processing_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable public access to the web service WSDL document using WLST:
To disable the WSDL access policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a WSDL access policy configured at a higher scope, attach the oracle/no_wsdl_request_processing_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_wsdl_request_processing_service_policy")
Policy reference "oracle/no_wsdl_request_processing_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable the processing of SOAP requests using WLST:
To disable the SOAP request processing policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a SOAP request processing policy configured at a higher scope, attach the oracle/no_wsdl_request_processing_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_soap_request_processing_service_policy")
Policy reference "oracle/no_soap_request_processing_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable an endpoint to receive non-SOAP XML messages that are processed by a user defined javax.xml.ws.Provider<T>.invoke
method using WLST:
To disable the non-SOAP XML message policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a non-SOAP XML message policy configured at a higher scope, attach the oracle/no_pox_http_binding_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_pox_http_binding_service_policy")
Policy reference "oracle/no_pox_http_binding_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To set the logging level for diagnostic logs for the web service endpoint using WLST:
To disable the log level policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a log level policy configured at a higher scope, attach the oracle/no_ws_logging_level_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_ws_logging_level_policy")
Policy reference "oracle/no_ws_logging_level_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
You can enable or disable the Web Services Test Client, as described in "Using the Web Services Test Client", at the domain or web service endpoint level:
"Enabling or Disabling the Web Services Test Client at the Domain Level Using WLST"
"Enabling or Disabling the Web Services Test Client at the Web Service Endpoint Level Using WLST"
Note:
The procedures described in this section do not impact the availability of the Web Services Test link on the Web Service Endpoint page, which enables you to access the Fusion Middleware Control Test Web Service page. For more information, see "Test Web Service Page in Fusion Middleware Control".
To enable or disable the web services Test Client at the domain level, use set the WebServiceTestEnable
property for the domain to true
to enable the test client and to false
to disable it.
For example, to enable the Web Services Test Client at the domain level using WLST:
wls:/wls-domain/serverConfig> edit() Location changed to edit tree. This is a writable tree with DomainMBean as the root. To make changes you will need to start an edit session via StartEdit(). For more help, use help('edit') wls:/mydomain/edit> startEdit() Starting an edit session ... Started edit session, please be sure to save and activate your changes once you are done. wls:/mydomain/edit> cd('WebserviceTestpage') wls:/mydomain/edit/WebserviceTestpage !> cd('new_domain') wls:/mydomain/edit/WebserviceTestpage/new_domain !> set('Enabled','true') wls:/mydomain/edit/WebserviceTestpage/new_domain !> save() Saving all your changes ... Saved all your changes successfully. wls:/mydomain/edit/WebserviceTestpage/new_domain !> activate() Activating all your changes, this may take awhile ... The edit lock associated with the edit session is released once the activation is complete. Activation completed wls:/mydomain/edit/WebserviceTestpage/new_domain !>
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable the web services test client at the web service endpoint level using WLST:
To disable the Web Services Test Client policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a Web Services Test Client policy configured at a higher scope, attach the oracle/no_ws_logging_level_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_test_page_processing_service_policy")
Policy reference "oracle/no_test_page_processing_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable the exchange of web service metadata using WLST:
To disable the metadata exchange policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a metadata exchange policy configured at a higher scope, attach the oracle/no_mex_request_processing_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_mex_request_processing_service_policy")
Policy reference "oracle/no_mex_request_processing_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable the creation of MTOM-encoded SOAP fault messages when MTOM is enabled using WLST:
To disable the MTOM-encoded fault message policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable an MTOM-encoded fault message policy configured at a higher scope, attach the oracle/no_mtom_encode_fault_service_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_mtom_encode_fault_service_policy")
Policy reference "oracle/no_mtom_encode)fault_service_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable the validation of request messages using WLST:
To disable the schema validation policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a schema validation policy configured at a higher scope, attach the oracle/no_schema_validation_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_schema_validation_policy")
Policy reference "oracle/no_schema_validation_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To set the maximum size of the request message using WLST:
To disable the maximum request size policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a maximum request size policy configured at a higher scope, attach the oracle/no_max_request_size_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_max_request_size_policy")
Policy reference "oracle/no_max_request_size_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
To enable and configure the binary caching of content using WLST:
To disable the binary content caching policy, perform one of the following steps:
Detach the policy. For more information, see "Detaching Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Disable the policy. For more information, see "Enabling and Disabling Directly Attached Policies Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
To disable a binary content caching policy configured at a higher scope, attach the oracle/no_cache_binary_content_policy
using the attachWSMPolicy
command. For complete details, see "Attaching Policies Directly Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
For example:
wls:/wls_domain/serverConfig> attachWSMPolicy("oracle/no_cache_binary_content_policy")
Policy reference "oracle/no_cache_binary_content_policy" added.
For more information about the WLST commands, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.
Use the following procedure to configure the web service client endpoint (port) using WLST:
For more information about these WLST commands and their arguments, see "Web Services Custom WLST Commands" in WLST Command Reference for Infrastructure Components.