The following sections describe the WebLogic Scripting Tool (WLST) commands for Oracle Infrastructure Web services (which includes ADF Business Components), Java EE Web services, and RESTful Web services. You can use these commands to manage Web services from the command line.
Note:
Only a subset of the custom WLST commands described in this chapter are supported for Java EE Web services.
A subset of WLST commands have been deprecated for Oracle Infrastructure Web services and clients. For a complete list of deprecated commands, see "Deprecated Commands for Oracle Infrastructure Web Services" in Release Notes.
Topics in this chapter include:
For additional details about using these WLST commands for Web services, see the following documents:
Notes:
To use the Web Services custom WLST commands, you must invoke WLST from the Oracle Common home directory. See "Using Custom WLST Commands" in the Administering Oracle Fusion Middleware.
To display the help for the Web service and client management and Java EE Web service policy management commands, connect to a running instance of the server and enter help('WebServices').
To display the help for the remaining commands, connect to a running instance of the server and enter help('wsmManage').
You can use the Web services WLST commands, in online mode, to:
Perform Web service configuration and OWSM policy management tasks.
Manage the OWSM repository.
Check the status of OWSM components.
View and define trusted issuers and DN lists for SAML signing certificates.
Note:
Ensure that the user is mapped to the appropriate OWSM logical roles, based on the WLST operations you wish to perform. For more information, see "Modifying the User's Group or Role" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
The Web services WLST configuration and policy management commands perform many of the same management functions that you can complete using Fusion Middleware Control, such as managing deployed, active, and running Web services applications. They can be executed everywhere in WLST online mode, for example:
wls:/domain/serverConfig wls:/domain/domainRuntime
The following sections provide more information about using the WLST commands:
The Web service WLST commands configure a Web service for a specific application. Therefore, the application path name has to uniquely identify the application and the server instance to which it is deployed.
The following sections describe how to specify the application and service names to uniquely identify the Web service.
To specify a Web service application in a WLST command, use the following format:
[/domain/server/]application[#version_number]
Parameters shown in brackets [] are optional. The following examples show the sample format for a Web service application name:
/base_domain/AdminServer/HelloWorld#1_0 /base_domain/server1/HelloWorld#1_0
If there is only one deployed instance of an application in a domain, you may omit the domain/server parameter, as shown in the following example:
HelloWorld#1_0
In all other instances, the domain/server parameter is required. If it is not specified and WLST finds more than one deployment of the same application on different servers in the domain, you are prompted to specify the domain and the server names.
Web service and Web service client applications are deployed directly to WebLogic Server server instances. Each application is managed separately. For example, if the application myapp is deployed to both the AdminServer and server1 instances in the domain mydomain, then you need to issue configuration commands to each of the servers using the appropriate application path name:
/mydomain/AdminServer/myapp#1_0 /mydomain/server1/myapp#1_0
When there are multiple versions (namespaces) of a Web service name for Web Service and Web Service clients, you must specify the namespace and the service name using the following format:
{http://namespace/}serviceName
Note the following:
For Web service and client management commands, and policy management commands, you do not need to enter the namespace if there is only one service name qualified. If there are multiple versions of the service and you do not specify the namespace with the service name, an exception is thrown.
For policy set management commands, both the namespace and service name are required for Web Service and Web Service Client (ws-service and ws-client) resource types.
For more information, see "Determining the Namespace for a Web Service" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Note:
This section applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
You can navigate to a policy subject in WLST, without having to refer to Fusion Middleware Control. By using the selectWSMPolicySubject command, together with an understanding of the navigation model, you can discover the application, assembly, and subject names by moving down the hierarchy tree.
You can select a specific application for modification if an application name is provided.
If you know only a part of the application name, the argument can be a pattern containing wildcard characters. In this case, all of the applications matching that pattern will be listed. You can then select that application to proceed further. If no argument is provided then all application names will be listed.
When the application name is known
If you know the name of the application, enter it as the argument to selectWSMPolicySubject command. WLST responds with the names of the assemblies contained in the application.
In the following example, jaxwsejb30ws is entered as the name of the application. WLST responds with #jaxwsejb, the name of the assembly contained in the application.
wls:/base_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws')
#jaxwsejb
Select any of the assembly name to proceed.
When only a part of the application name is known
If you know only a part of the application name, you can enter a pattern with wildcard characters. In the following example, jax* is entered as the name of the application in the selectWSMPolicySubject command. WLST responds with a list of applications that match the string.
wls:/base_domain/serverConfig> selectWSMPolicySubject('jax*')
jaxws_provider
jaxwsejb30ws
Select any of the application name to proceed.
wls:/jrfServer_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws')
#jaxws3jb
Select any of the assembly name to proceed
When the application name is not known
If you do not know the name of the application, enter the selectWSMPolicySubject command with no arguments. WLST responds with the names of all applications known to the system. In the following example, the selectWSMPolicySubject command is entered with no arguments. WLST responds with the names of all applications known to the system.
wls:/base_domain/serverConfig> selectWSMPolicySubject()
SimpleRestApp
jaxws_provider
jaxwsejb30ws
wsm-pm
Select any of the application name to proceed.
wls:/jrfServer_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws')
#jaxws3jb
Select any of the assembly name to proceed
You can select a specific assembly for modification if an application name and assembly name is provided.
If you know only a part of the assembly name, the argument can be a pattern containing wildcard characters. In this case, all of the assemblies matching that pattern will be listed. You can then select an assembly to proceed further. If no argument is provided then all assembly names will be listed.
Note:
For ws-connection type policy subjects, use an empty string '' for the assembly name.
When the assembly name is known
If you know the name of the assembly, enter it with the application name as arguments to the selectWSMPolicySubject command. WLST responds with the names of the subjects contained in the assembly. In the following example, jaxwsejb30ws is entered as the name of the application and #jaxwsejb is entered as the name of the assembly. WLST responds with a list of all of the subjects contained in the assembly.
wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb')
WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
WS-SERVICE({http://j2ee.tests.ejb.impl/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
Select any of the subject name to proceed.
When only a part of the assembly name is known
If you know only a part of the assembly name, you can enter a pattern with wildcard characters. In the following example, #jaxws* is entered as the partial name of the assembly and jaxwsejb30ws is entered as the name of the application in the selectWSMPolicySubject command. WLST responds with #jaxwsejb, the name of the assembly contained in the application.
wls:/base_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws','#jaxws*')
#jaxwsejb
Select any of the assembly name to proceed.
wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb')
WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
WS-SERVICE({http://j2ee.tests.ejb.impl/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
Select any of the subject name to proceed.
When the assembly name is not known
If you do not know the name of the assembly, enter the name of the application only as an argument to selectWSMPolicySubject. WLST responds with the names of all assemblies known to the system. In the following example, jaxwsejb30ws is entered as the name of the application as an argument in selectWSMPolicySubject command. WLST responds with the names of all assemblies known to the system.
wls:/base_domain/serverConfig> selectWSMPolicySubject('jaxwsejb30ws')
#jaxwsejb
Select any of the assembly name to proceed.
You can select a specific policy subject for modification if an application name, assembly name, and policy subject name is provided.
If you know only a part of the policy subject name, the argument can be a pattern containing wildcard characters. In this case, all of the policy subjects matching that pattern will be listed. You can then select a policy subject to proceed further. If no argument is provided then all policy subject names will be listed.
When the policy subject name is known
If you know the name of the policy subject, enter it with the application name and the assembly name as arguments to the selectWSMPolicySubject command. WLST selects the specified policy subject. In the following example, jaxwsejb30ws is entered as the name of the application, #jaxwsejb is entered as the name of the assembly, and WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort) is entered as the name of the policy subject. WLST responds that the policy subject has been selected for modification.
wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb','WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)')
The policy subject is selected for modification.
When only a part of the policy subject name is known
If you know only a part of the policy subject name, you can enter a pattern with wildcard characters. In the following example, jaxwsejb30ws is entered as the name of the application, #jaxwsejb is entered as the name of the assembly, and ws-service(*) is entered as the name of the policy subject in the selectWSMPolicySubject command. WLST responds with the name of the policy subjects contained in the assembly.
wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb', 'ws-service(*)')
WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
WS-SERVICE({http://j2ee.tests.ejb.impl/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
Select any of the subject name to proceed.
When the policy subject name is not known
If you do not know the name of the policy subject, enter the name of the application, the name of the assembly as arguments to the selectWSMPolicySubject command. WLST responds with the names of all policy subjects contained in the assembly. In the following example, jaxwsejb30ws is entered as the name of the application, #jaxwsejb as the name of the assembly, and None as the policy subject argument in selectWSMPolicySubject command. WLST responds with the names of all policy subjects contained in the assembly.
wls:/base_domain/serverConfig> selectWSMPolicySubject ('jaxwsejb30ws','#jaxwsejb')
WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
WS-SERVICE({http://j2ee.tests.ejb.impl/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
Select any of the subject name to proceed.
Web services WLST commands are divided into the categories described in Table 3-1.
Table 3-1 Web Services WLST Command Categories
| Command Category | Definition |
|---|---|
|
Manage a session, which is required by some Web service WLST commands, such as those that modify repository documents and policy subject commands, need to be executed in the context of a session. |
|
|
View and manage Web service and Web service client policy subjects. |
|
|
View and manage OWSM domain configuration information. |
|
|
Check the status of the WSM components that are required for proper functioning of the product. |
|
|
View and manage Web services for the service and client. |
|
|
View and manage policy attachment for the service and client. These commands manage both direct policy attachments and global policy attachments in policy sets. |
|
|
View and manage globally available policy sets within sessions. |
|
|
Manage the OWSM repository with new predefined policies provided in the latest installation of the software, as well as import and export documents into and from the repository. |
|
|
View and define trusted issuers, trusted distinguished name (DN) lists, and token attribute rule filters for SAML signing certificates. |
Some Web service WLST commands, such as those that modify repository documents and policy subject commands, need to be executed in the context of a session. Use the WLST commands listed in Table 3-2 to manage a session.
Note:
The commands in this section apply to Oracle Infrastructure and RESTful Web services. They do not apply to Java EE Web services in this release.
Table 3-2 Session Management WLST Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Abort the current modification session, discarding any changes that were made to the repository during the session. |
Online |
|
|
Begin a session to modify a policy subject or the OWSM repository documents. |
Online |
|
|
Write the contents of the current session to the OWSM repository. |
Online |
|
|
Describe the contents of the current session. This will indicate either that the session is empty or list the name of the document that is being updated, along with the type of update (create, modify, or delete). |
Online |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Session
Use with WLST: Online
Aborts the current modification session, discarding any changes that were made during the session. Messages are displayed that describe what was aborted.An error will be displayed if there is no current session.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Session
Use with WLST: Online
Begins a session to modify a policy subject, such as a policy set or a Fusion Middleware Web service endpoint. A session can act on a single policy subject only. If a session is already in progress, an error is displayed.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Session
Use with WLST: Online
Persists the modifications made within the current session. Messages are displayed that describe what was committed. An error will be displayed if there is no current session.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Session
Use with WLST: Online
Describes the current session. For repository operations, it will either indicate that no actions have been performed in the session, or it will list the name of the document that is being updated, along with the type of update, such as create, modify, or delete. For policy subject operations, it will list the subject identifier.
If there is no current session, the following error is displayed:
No actions in session.
Use the WLST commands listed in Table 3-3 to view and manage Web service and Web service client policy subjects. For more information about policy subjects, see "Understanding Policy Subjects" in Understanding Oracle Web Services Manager.
Note:
For Java EE Web services, no information is displayed. For information about viewing and modifying Java EE Web service policy attachments, see Table 3-7.
Table 3-3 Policy Subject WLST Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Display the configuration of effective policy set corresponding to a policy subject. |
Online |
|
|
List the policy subjects that match the specified application, assembly, and subject patterns. |
Online |
|
|
Displays the configuration of an effective policy set corresponding to a policy subject. The display will also include any changes made within the current session when it generates the effective policy set. |
Online |
|
|
Select the subject uniquely identified by application, assembly and subject for modification. |
Online |
Command Category: Policy Subject
Use with WLST: Online
Note:
This command is valid for Oracle Infrastructure Web service and clients only. For Java EE Web services, no information is displayed. For information about viewing and modifying Java EE Web service policy attachments, see Table 3-7.
Displays the configuration of the actual runtime policy set and global policy attachment information used at the time of policy enforcement. This policy set and global policy attachment information is stored within the policy subject.
You must start a session and select the policy subject (using selectWSMPolicySubject) before initiating the command. If there is no current session and no policy subject selected, an error is displayed.
Compare this command with the "displayWSMPolicySet" command, which displays only the selected global policy set or the selected local policy set, or with the "previewWSMEffectivePolicySet", which displays the effective policy set, including changes made to the actual runtime policy set, within the current session.
The following example for an Oracle Infrastructure Web service lists that the policies, oracle/wss_username_token_service_policy and oracle/log_policy, are in effect at the time of enforcement.
wls:/jrfServer_domain/serverConfig> selectWSMPolicySubject('/weblogic/jrfServer_domain/jaxws-sut','#jaxws-sut-service','WS-SERVICE({http://service.jaxws.wsm.oracle/}TestService#TestPort)')
The policy subject is selected for modification.
wls:/jrfServer_domain/serverConfig> displayWSMEffectivePolicySet()
Command Category: Policy Subject
Use with WLST: Online
Lists the policy subjects that match the specified application, assembly, and subject patterns. You can use the optional detail argument to include effective policy set information in the output. The command does not require starting a session.
For more information about the pattern used to identify a subject, see Identifying the Policy Subject.
listWSMPolicySubjects([application=None],[assembly=None],[subject=None],[detail='false'])
| Argument | Definition |
|---|---|
|
|
Optional. Pattern identifying applications. |
|
|
Optional. Pattern identifying assemblies. |
|
|
Optional. Pattern identifying subjects. |
|
|
Optional. Specifies whether to include effective policy set information in the output. The default value is |
To simplify searching for a particular subject, the application, assembly, or subject argument can specify a pattern containing the wildcard character (*). In this case, all the subjects matching that pattern will be listed.
The following invocation of the listWSMPolicySubjects command with detail='true' returns the application, assembly, and subject information for all subjects being managed in base_domain.
wls:/base_domain/serverConfig> listWSMPolicySubjects(detail='true')
Application: /weblogic/base_domain/SimpleRestApp
Assembly: #SimpleRestApp
Subject: WS-SERVICE({http://rest.jaxws.ws.j2ee.oracle/}SimpleRestServiceService#SimpleRestServicePort)
The web service is not secure in this context.
Application: /weblogic/base_domain/jaxwsejb30ws
Assembly: #jaxwsejb
Subject: WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
The web service is not secure in this context.
Subject: WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
The web service is not secure in this context.
Subject: WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
The web service is not secure in this context.
Subject: WS-SERVICE({http://soapinterop.org/DoclitWrapperWTJ}DoclitWrapperWTJService#DoclitWrapperWTJPort)
The web service is not secure in this context.
Subject: WS-SERVICE({http://j2ee.tests.ejb.impl/}JaxwsWithHandlerChainBeanService#JaxwsWithHandlerChainBeanPort)
The web service is not secure in this context.
Application: /weblogic/base_domain/wsm-pm
Assembly: #Diagnostic
Subject: WS-SERVICE({http://diagnostic.jaxws.wsmtest/}DiagnosticService#DiagnosticPort)
URI="oracle/wss_saml_or_username_token_service_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
The web service is secure in this context.
Invoking the listWSMPolicySubjects command with ('jax*') as the argument returns all subjects belonging to the jaxwsejb30ws application:
wls:/base_domain/serverConfig> listWSMPolicySubjects('jax*')
Application: /weblogic/base_domain/jaxwsejb30ws
Assembly: #jaxwsejb
Subject: WS-SERVICE({http://mycompany.com/targetNamespace}EchoEJBService#EchoEJBServicePort)
Subject: WS-SERVICE({http://mycompany.com/jaxws/tests/concrete}WsdlConcreteService#WsdlConcretePort)
Subject: WS-SERVICE({http://mycompany.com/jaxws/tests}CalculatorService#CalculatorPort)
Command Category: Policy Subject
Use with WLST: Online
Displays the configuration of the effective policy set corresponding to the policy subject. The display will also include any changes made within current session when it generates the effective policy set.
You must start a session and select the policy subject (using selectWSMPolicySubject) before initiating the command. An error will display if no policy subject is selected.
See also "displayWSMEffectivePolicySet", which displays the actual policy set used at the time of enforcement, but does not display any changes made to the policy set during the current session.
Command Category: Policy Subject
Use with WLST: Online
Within a session, selects a policy subject for modification. You uniquely specify a policy subject by the application, assembly, and policy subject name. Once selected, the policy management commands can be used to modify the directly attached policy set for the policy subject.
You must start a session (beginWSMSession) before performing any policy management edits or policy set transactions. You must also select the policy subject that you want to modify before issuing policy management commands. If there is no current session or there is already an existing modification process, an error is displayed.
For more information on using this command, see "Identifying the Policy Subject" and "Identifying and Selecting the Policy Subject Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
selectWSMPolicySubject([application=None],[assembly=None],[subject=None])
| Argument | Description |
|---|---|
|
application |
Name of the application. |
|
assembly |
Name of the assembly. Uniquely identifies the module within an application. |
|
subject |
Name of the policy subject. |
Note:
Any of the three arguments can specify a pattern containing wildcard character "*". In this case, all the names matching that pattern will be listed. You need to select the name uniquely identifying the subject. The pattern can be specified only for the last unknown entity.
The following example selects the TestService#TestPort port in the jaxws-sut-service module (assembly) that belongs to the jaxws-sut application. See "Identifying the Policy Subject" for additional examples.
wls:/jrfServer_domain/serverConfig> selectWSMPolicySubject('/weblogic/jrfServer_domain/jaxws-sut','#jaxws-sut-service','WS-SERVICE({http://service.jaxws.wsm.oracle/}TestService#TestPort)')
The policy subject is selected for modification.
Use the WLST commands listed in Table 3-4 to view and configure the OWSM domain.
Note:
The setConfiguration command has been deprecated. It is recommended that you use the setWSMConfiguration command described in "setWSMConfiguration".
Table 3-4 OWSM Environment WLST Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Set the keystore configuration properties. |
Online |
|
|
Display the full configuration properties and their values and groups for the specified product. |
Online |
|
|
Set the configuration properties of the specified product. |
Online |
Command Category: Configuration
Use with WLST: Online
Sets the configuration properties for the OWSM keystore.
For more information, see "Configuring the OWSM Keystore Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Note:
Changes to the keystore configuration at the domain level require that you restart the server.
configureWSMKeystore(context, keystoreType, location, keystorePassword, signAlias, signAliasPassword, cryptAlias, cryptAliasPassword)
| Arguments | Description |
|---|---|
|
|
Optional. The context of the configuration document in which the modifications will be done. |
|
|
Optional. The keystore type category of the property. Valid keystore types are |
|
|
Optional. For JKS, it is the absolute location of the keystore or location relative to the |
|
|
Optional. The keystore password of the keystore configured. It is required for |
|
|
Optional. The Alias of the sign key. It is required for |
|
|
Optional. Password of the |
|
|
Optional. The |
|
|
Optional. Password of the |
The following example configures the JKS keystore default-keystore.jks in the domain myDomain. It provides the keystore password oratest123, the sign alias oraAlias, the sign alias password ora234, the encryption alias oraCryptAlias, the encryption alias password ora123.
wls:/jrfServer_domain/serverConfig> configureWSMKeystore ('/WLS/myDomain','JKS', './default-keystore.jks','oratest123', 'oraAlias','ora234','oraCryptAlias', 'ora123')
The following example configures the KSS keystore at kss://owsm/keystore in the domain myDomain. It provides the sign alias oraAlias, and the encryption alias oraCryptAlias.
wls:/jrfServer_domain/serverConfig> configureWSMKeystore ('/WLS/myDomain',keystoreType='KSS', location='kss://owsm/keystore', signAlias='oraAlias', cryptAlias='encAlias')
Command Category: Configuration
Use with WLST: Online
Displays the full set of configuration properties, and their values and groups, for the product specified in the context. If a property is not defined in the configuration document associated with the context, then the default value defined for the product is displayed. If a context is not specified, then the set of properties matching the current context is displayed.
For more information, see "Managing OWSM Domain Configuration Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
displayWSMConfiguration([context=None])
| Arguments | Description |
|---|---|
|
|
Optional. The context of the configuration document from which property values are displayed. If a To display the default set of properties along with their values, use "/" as the context value." |
The following example displays the configuration contained in the configuration document in the repository.
wls:/jrfServer_domain/serverConfig> displayWSMConfiguration()
The following example displays the configuration for the base_domain domain.
wls:/jrfServer_domain/serverConfig> displayWSMConfiguration('WLS/base_domain')
Command Category: Configuration
Use with WLST: Online
Note:
This command has been deprecated. It is recommended that you use the setWSMConfiguration command described in "setWSMConfiguration".
Sets the configuration properties of a domain. The properties are stored in a configuration document for the domain. If a configuration document does not exist, a new one is created.
A new property with values and/or groups of values can be added inside the configuration document. The set of acceptable properties is determined from the default set of properties supported by the product. Specific property values or groups of values can be removed from the configuration document. The configuration document itself is removed if no properties exist in it.
setConfiguration(context, category, name, [group=None], [values=None])
| Arguments | Description |
|---|---|
|
|
Optional. The context of the configuration document to be modified for the product. If a context is not provided or is set to |
|
|
The category of the property. This is verified against the default set of properties to ensure it is acceptable for the context. Use the displayWSMConfiguration command to see the category name associated with each property. |
|
|
The name of the property. This is verified with the default set of properties for acceptability. |
|
|
Optional. A group containing the set of values to add in a property document. If set to |
|
|
Optional. The array of values to set for a property or group inside the property document. |
The following example resets the entire configuration for the domain myDomain to its default values.
wls:/jrfServer_domain/serverConfig> setConfiguration('/WLS/myDomain')
The following command resets the value of the clock.skew property in myDomain to 500.
wls:/jrfServer_domain/serverConfig> setConfiguration('/WLS/myDomain','Agent','clock.skew',None, ['500'])
The following command resets the value of the clock.skew property in myDomain to its default value.
wls:/jrfServer_domain/serverConfig> setConfiguration('/WLS/myDomain','Agent','clock.skew',None,None)
Command Category: Configuration
Use with WLST: Online
Sets the configuration properties of a domain. The properties are stored in a configuration document for the domain. If a configuration document does not exist, a new one is created.
A new property with values and/or groups of values can be added inside the configuration document. The set of acceptable properties is determined from the default set of properties supported by the product. Specific property values or groups of values can be removed from the configuration document. The configuration document itself is removed if no properties exist in it.
For more information, see "Managing OWSM Domain Configuration Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
setWSMConfiguration(context, category, name, [group=None], [values=None])
| Arguments | Description |
|---|---|
|
|
Optional. The context of the configuration document to be modified. If a context is not provided or is set to |
|
|
The category of the property. This is verified against the default set of properties to ensure it is acceptable for the context. Use the displayWSMConfiguration command to see the category name associated with each property. |
|
|
The name of the property. This is verified against the default set of properties to ensure it is acceptable for the context. |
|
|
Optional. A group containing the set of values to add in a configuration document. If the group exists, and this value is set to |
|
|
Optional. The array of values to set for a property or group inside the configuration document. |
The following example resets the entire configuration for the domain myDomain to its default values.
wls:/jrfServer_domain/serverConfig> setWSMConfiguration('/WLS/myDomain')
The following command resets the value of the clock.skew property in myDomain to 500.
wls:/jrfServer_domain/serverConfig> setWSMConfiguration('/WLS/myDomain','Agent','clock.skew',None, ['500'])
The following command resets the value of the clock.skew property in myDomain to its default value.
wls:/jrfServer_domain/serverConfig> setWSMConfiguration('/WLS/myDomain','Agent','clock.skew',None,None)
Use the WLST command in this section to check the status of the WSM components that are required for proper functioning of the product.
Command Category: Diagnostic
Use with WLST: Online
Checks the status of the OWSM components that are required for proper functioning of the product. The OWSM components that are checked are the Policy Manager (wsm-pm), the agent (agent), and the credential store and keystore configuration. The status of the components can be checked together or individually.
Note:
The Policy Manager (wsm-pm) application must be deployed and running for the check status tool to function correctly.
checkWSMStatus([component=None],[address=None],[verbose=true])
| Arguments | Description |
|---|---|
|
|
Optional. All checks will be performed if no value is specified. Valid options are:
|
|
|
Optional. The HTTP URL of the host running the
checkWSMStatus('agent', 'http://localhost:7001')
The address is not required in the WebLogic Server domain where auto-discovery is present. |
|
|
Optional. If the value of this flag is |
In the following example, the checkWSMStatus command is run without arguments. The status of the credential store, policy manager, and enforcement agent is returned.
wls:/base_domain/serverConfig> checkWSMStatus()
Credential Store Configuration:
PASSED.
Message(s):
keystore.pass.csf.key : Property is configured and its value is "keystore-csf-key".
Description: The "keystore.pass.csf.key" property points to the CSF alias that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
keystore-csf-key : Credentials configured.
keystore.sig.csf.key : Property is configured and its value is "sign-csf-key".
Description: The "keystore.sig.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for signing.
sign-csf-key : Credentials configured.
Sign Key : Key configured.
Alias - orakey
Sign Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT
keystore.enc.csf.key : Property is configured and its value is "enc-csf-key".
Description: The "keystore.enc.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for decryption.
enc-csf-key : Credentials configured.
Encrypt Key : Key configured.
Alias - orakey
Encrypt Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT
Policy Manager:
PASSED.
Message(s):
OWSM Policy Manager connection state is OK.
OWSM Policy Manager connection URL is "host.example.com:1234".
Enforcement Agent:
PASSED.
Message(s):
Enforcement is successful.
Service URL: http://host:port/Diagnostic/DiagnosticService?wsdl
In the following example, the credential store key keystore-csf-key is deleted and the checkWSMStatus command is rerun for the credential store credstore. The status check fails because the csf-key keystore-csf-key is not present in the credential store:
wls:/base_domain/serverConfig> deleteCred(map="oracle.wsm.security", key="keystore-csf-key")
wls:/base_domain/serverConfig> checkWSMStatus('credstore')
Credential Store Configuration:
FAILED.
Message(s):
keystore.pass.csf.key : Property is configured and its value is "keystore-csf-key".
Description: The "keystore.pass.csf.key" property points to the CSF alias that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
keystore-csf-key : Credentials not configured.
Credential Store Diagnostic Messages:
Message(s):
The csf-key keystore-csf-key is not present in the credential store.
Perform the following steps to update the credential store (using WLST commands):-
1. connect()
2. createCred(map="oracle.wsm.security", key="keystore-csf-key", user="keystore-csf-key", password="<keystore-password>", desc="Keystore Password CSF Key")
NOTE:- All the above commands are based on the Domain level configurations. The actual csf key may be overridden at runtime due to config override. See Documentation for more details.
In the following example, the csf-key keystore-csf-key is configured and the checkWSMStatus command is rerun. The configuration check passes.
wls:/base_domain/serverConfig> createCred(map="oracle.wsm.security", key="keystore-csf-key", user="keystore-csf-key", password="welcome1", desc="Keystore Password CSF Key")
Already in Domain Runtime Tree
wls:/base_domain/serverConfig> checkWSMStatus('credstore')
Credential Store Configuration:
PASSED.
Message(s):
keystore.pass.csf.key : Property is configured and its value is "keystore-csf-key".
Description: The "keystore.pass.csf.key" property points to the CSF alias that is mapped to the username and password of the keystore. Only the password is used; username is redundant in the case of the keystore.
keystore-csf-key : Credentials configured.
keystore.sig.csf.key : Property is configured and its value is "sign-csf-key".
Description: The "keystore.sig.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for signing.
sign-csf-key : Credentials configured.
Sign Key : Key configured.
Alias - orakey
Sign Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT
keystore.enc.csf.key : Property is configured and its value is "enc-csf-key".
Description: The "keystore.enc.csf.key" property points to the CSF alias that is mapped to the username and password of the private key that is used for decryption.
enc-csf-key : Credentials configured.
Encrypt Key : Key configured.
Alias - orakey
Encrypt Certificate : Certificate configured.
Alias - CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US
Expiry - June 28, 2020 11:17:12 AM PDT
true
The following example checks the enforcement status of the agent component at the URL http://localhost:7001.
wls:/test_domain1/serverConfig> checkWSMStatus('agent','http://localhost:7001')
Enforcement Agent:
Note: Enforcement might succeed if OWSM Policy Manager is down due to policy caching. For such scenarios wsm-pm test must be run prior to this test.
PASSED.
Message(s):
Enforcement is successful.
Service URL: http://localhost:7001/Diagnostic/DiagnosticService?wsdl
Use the WLST commands listed in Table 3-5 to view and manage Web services for deployed, active, and running Web service applications.
Table 3-5 Web Service and Client Management WLST Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
List Web service client ports information for an application. |
Online |
|
|
List Web service client information for an application or domain. |
Online |
|
|
List Web service client port stub properties for an application. |
Online |
|
|
List the Web service ports for a Web service application. |
Online |
|
|
List the Web service information for an application or domain. |
Online |
|
|
Configure the set of stub properties of a Web service client port for an application. |
Online |
|
|
Set, change, or delete a single stub property of a Web service client port for an application. |
Online |
Command Category: Web Service and Client Management
Use with WLST: Online
Lists the Web service port names and the endpoint URLs for Web service clients in an application.
The output will display the name of the Web service client/reference port. For example:
AppModuleServiceSoapHttpPort
listWebServiceClientPorts(application,moduleOrCompName,moduleType,serviceRefName)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web services port information. For example, To list the client port information for an application, this argument is required. |
|
|
Name of the Web module for which you want to list the Web service client port information. |
|
|
Module type. Valid options are:
|
|
|
Service reference name of the application for which you want to list the Web service client port information. When the client is an asynchronous Web service callback client, the |
The following example lists the client ports for the WssUsernameClient Web module in the /base_domain/server1/jwsclient_1#1.1.0 application. Note that the moduleType is set to wsconn, and the serviceRefName is set to WssUsernameClient.
wls:/base_domain/serverConfig> listWebServiceClientPorts ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient')
Command Category: Web Service and Client Management
Use with WLST: Online
Lists Web service clients information for an application or domain. If an application is not specified, the command lists information about all Web service clients in all applications for every server instance in the domain.
You can specify the amount of information to be displayed in the output using the detail argument. When specified, the output provides endpoint (port) and policy details for clients in the domain, the secure status of the endpoints, any configuration overrides and constraints, and if the endpoints have a valid configuration. A subject is considered secure if the policies attached to it (either directly or globally) enforce authentication, authorization, or message protection behaviors. Because you can specify the priority of a global or directly attached policy (using the reference.priority configuration override), the effective field indicates if the directly attached policies are in effect for the endpoint.
Note that to simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect. In contrast, only globally attached policies that are in effect for the endpoint are displayed. For more information, see "How the Effective Set of Policies is Calculated" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
The output is listed by each application deployed as shown in the following examples:
This example shows the output of an unsecured endpoint:
wls:/jrfServer_domain/serverConfig> listWebServiceClients(detail=true)
/jrfServer_domain/jrfServer_admin/ADFDCDecoupling_Project1_ADFDCDecoupling :
moduleName=testadfbc, moduleType=wsconn, serviceRefName=AppModuleService
AppModuleServiceSoapHttpPort
The policy subject is not secure in this context.
This example shows the output for a secured endpoint:
wls:/jrfServer_domain/serverConfig> listWebServiceClients(detail=true)
/jrfServer_domain/jrfServer_admin/ADFDCDecoupling_Project1_ADFDCDecoupling :
moduleName=testadfbc, moduleType=wsconn, serviceRefName=AppModuleService
AppModuleServiceSoapHttpPort serviceWSDLURI=http://host.example.com:1234/ADFBCDecoupling-ADFBCDecoupling-context-root/AppModuleService?wsdl
URI="oracle/wss10_saml_token_with_message_protection_client_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true
The policy subject is secure in this context.
listWebServiceClients(application,[detail])
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web service clients. For example, If specified, all Web services clients in the application are listed. |
|
|
Optional. Specifies whether to list port and policy details for the Web service clients. Valid values are:
|
The following example lists information for all Web service clients in the domain.
wls:/wls-domain/serverConfig>listWebServiceClients()
The following example lists the Web service clients for the application jwsclient_1#1.10 for the server server1 in the domain base_domain.
wls:/wls-domain/serverConfig>listWebServiceClients('base_domain/server1/jwsclient_1#1.10')
The following example lists details for all of the Web service clients in the domain.
wls:/wls-domain/serverConfig>listWebServiceClients(None,None,true)
Note:
This command applies to Oracle Infrastructure Web service clients only.
Command Category: Web Service and Client Management
Use with WLST: Online
listWebServiceClientStubProperties(application, moduleOrCompName, moduleType, serviceRefName, portInfoName)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web services client port stub properties. For example, To list the client port stub properties information for an application, this argument is required. |
|
|
Name of the Web module for which you want to list the Web services client port stub properties. |
|
|
Module type. Valid options are:
|
|
|
Service reference name of the application for which you want to list the Web service client port stub properties. |
|
|
The name of the client port for which you want to list the stub properties. |
The following example lists the client port stub properties for the JRFWssUsernamePort port of the WssUsernameClient Web module in the /base_domain/server1/jwsclient_1#1.1.0 application. Note that the moduleType is set to wsconn, and the serviceRefName is set to WssUsernameClient.
wls:/base_domain/serverConfig>listWebServiceClientStubProperties ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort')
Command Category: Web Service and Client Management
Use with WLST: Online
Lists the Web service port names and the endpoint URLs for a Web service application.
The output will display the port name and endpoint URL of the Web service port. For example:
JRFWssUsernamePort http://localhost:7001/j2wbasicPolicy/WssUsername
listWebServicePorts(application,moduleOrCompName,moduleType,serviceName)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web services port information. For example, To list the port information for an application, this argument is required. |
|
|
Name of the Web module for which you want to list the Web services port information. |
|
|
Module type. Valid options are:
|
|
|
Name of the Web service in the application for which you want to list the port information. For example, { |
The following example lists the Web service ports and endpoint URLs for the Oracle Infrastructure Web service j2wbasicPolicy service in the base_domain/AdminServer/HelloWorld#1_0 application. Note that the WssUsernameService module name is specified, and the moduleType is set to web.
wls:/base_domain/serverConfig> listWebServicePorts ( '/base_domain/AdminServer/HelloWorld#1_0', 'WssUsernameService','web','{http://namespace/}j2wbasicPolicy') JRFWssUsernamePort http://localhost:7001/j2wbasicPolicy/WssUsername
The following example lists the Web service ports and endpoint URLs for the Java EE Web service helloWorldJaxws in the wls-domain/AdminServer/helloWorldJaxws application. Note that the moduleType is set to wls.
wls:/wls-domain/serverConfig> listWebServicePorts ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws')
helloWorldJaxwsSoapHttpPort
Command Category: Web Service and Client Management
Use with WLST: Online
Lists the Web service information for an application or domain. If you don't specify a Web service application, the command lists all services in all applications for every server instance in the domain.
You can specify the amount of information to be displayed in the output using the detail argument. When specified, the output provides endpoint (port) and policy details for all applications in the domain, the secure status of the endpoints, any configuration overrides and constraints, and if the endpoints have a valid configuration. A subject is considered secure if the policies attached to it (either directly or globally) enforce authentication, authorization, or message protection behaviors. Because you can specify the priority of a global or directly attached policy (using the reference.priority configuration override), the effective field indicates if the directly attached policies are in effect for the endpoint.
Note that to simplify endpoint management, all directly attached policies are shown in the output regardless of whether they are in effect. In contrast, only globally attached policies that are in effect for the endpoint are displayed. For more information, see "How the Effective Set of Policies is Calculated" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
The output is listed by each application deployed as shown in the following example:
/domain/server/application#version_number:
moduleName=helloModule, moduleType=web, serviceName={http://namespace/}service
Notes:
For applications assembled prior to 11g Release 1, (11.1.1.6), the namespace is not displayed with the serviceName in the output.
listWebServices (application,[detail])
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web services. For example, If specified, all Web services in the application are listed. |
|
|
Optional. Specifies whether to list port and policy details for the Web service. Valid values are:
|
The following example for an Oracle Infrastructure Web service lists all the Web services in all applications in the domain. Sample output is shown in this example.
wls:/base_domain/serverConfig> listWebServices()
/base_domain/AdminServer/jaxwsejb30ws :
moduleName=jaxwsejb, moduleType=web, serviceName=JaxwsWithHandlerChainBeanService
moduleName=jaxwsejb, moduleType=web, serviceName=WsdlConcreteService
moduleName=jaxwsejb, moduleType=web, serviceName=EchoEJBService
moduleName=jaxwsejb, moduleType=web, serviceName=CalculatorService
moduleName=jaxwsejb, moduleType=web, serviceName=DoclitWrapperWTJService
The following example for an Oracle Infrastructure Web service sets the detail argument to true. Sample output is shown in this example. Note that the reference priority of the globally attached policy to 10 and the directly attached policy is not in effect for the endpoint CalculatorPort in the application jaxwsejb30ws. Security policies are shown in bold text.
wls:/base_domain/serverConfig> listWebServices(detail='true') /base_domain/AdminServer/jaxwsejb30ws : moduleName=jaxwsejb, moduleType=web, serviceName=CalculatorService CalculatorPort http://host.example.com:1234/jaxwsejb/Calculator URI="oracle/wss10_saml20_token_with_message_protection_service_policy", category=security, policy-status=enabled; source=global policy set " MyPolicySet1", scope="DOMAIN('*')"; reference-status=enabled; effective=true Property name="reference.priority", value="10" URI="oracle/mex_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/mtom_encode_fault_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/max_request_size_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true Property name="max.request.size", value="-1" URI="oracle/request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/soap_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/ws_logging_level_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true Property name="logging.level", value="" URI="oracle/test_page_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/wsdl_request_processing_service_policy", category=wsconfig, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true URI="oracle/http_saml20_token_bearer_service_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=false The policy subject is secure in this context.
The following example for a Java EE Web service sets the detail argument to true. Sample output is shown in this example. The output lists all the Web services in all applications in the domain.
/base_domain/AdminServer/simpleJAXWS :
moduleName=SimpleJAXWS#1!SimpleEjbService, moduleType=wls, serviceName=SimpleEjbService
SimplePort
The policy subject is not secure in this context.
Note:
This command applies to Oracle Infrastructure Web service clients only.
Command Category: Web Service and Client Management
Use with WLST: Online
Configures the set of stub properties of a Web service client port for an application.
This command configures or resets all of the stub properties for the OWSM client security policy attached to the client. Each property that you list in the command is set to the value you specify. If a property that was previously set is not explicitly specified in this command, it is reset to the default for the property. If no default exists, the property is removed.
setWebServiceClientStubProperties(application, moduleOrCompName, moduleType, serviceRefName, portInfoName, properties)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to reset the Web services client port stub properties. For example, To configure or reset the client port stub properties for an application, this argument is required. |
|
|
Name of the Web module for which you want to reset the Web services client port stub properties. |
|
|
Module type. Valid options are:
|
|
|
Service reference name of the application for which you want to reset the Web service client port stub properties. |
|
|
The name of the client port for which you want to reset the stub properties. |
|
|
The list of properties to be set or changed. Properties must be specified using the following format:
For example:
To remove a property or clear the value assigned to it, specify a blank
To remove all the properties of the client port, set this argument to Sample client port stub properties are as follows:
|
The following example resets the client port stub properties ROLE and keystore.recipient.alias to ADMIN and orakey, respectively. Any other properties that were previously set for this client port are either reset to the default or removed. The client port is JRFWssUsernamePort of the WssUsernameClient Web module in the /base_domain/server1/jwsclient_1#1.1.0 application. Note that the moduleType is set to wsconn, and the serviceRefName is set to WssUsernameClient.
wls:/base_domain/serverConfig>setWebServiceClientStubProperties('/base_domain/server1/jwsclient_1#1.1.0', 'WssUsernameClient','wsconn','WssUsernameClient','JRFWssUsernamePort', [("ROLE","ADMIN"),("keystore.recipient.alias","orakey")] )
Command Category: Web Service and Client Management
Use with WLST: Online
Sets, changes, or deletes a single stub property of a Web service client port for an application.
setWebServiceClientStubProperty(application, moduleOrCompName, moduleType, serviceRefName,portInfoName,propName,[propValue])
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to set the Web services client port stub property. For example, To set a client port stub property for an application, this argument is required. |
|
|
Name of the Web module for which you want to set the Web services client port stub property. |
|
|
Module type. Valid options are:
|
|
|
Service reference name of the application for which you want to set the Web service client port stub property. |
|
|
The name of the client port for which you want to set the stub property. |
|
|
Stub property name that you want to set, change, or delete. For example, |
|
|
Optional. The stub property value, for example, To remove the property, specify a blank |
The following example sets the client port stub property keystore.recipient.alias to the value orakey for the client port JRFWssUsernamePort. The port is a client port of the WssUsernameClient Web module in the /base_domain/server1/jwsclient_1#1.1.0 application. Note that the moduleType is set to wsconn, and the serviceRefName is set to WssUsernameClient.
wls:/base_domain/serverConfig>setWebServiceClientStubProperty ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort','keystore.recipient.alias','orakey')
Note:
The policy management commands for Java EE Web Services (or clients) listed in Table 3-7 have been deprecated in this release for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web services, to manage OWSM directly attached policies in release 12c, it is recommended that you use the new WLST commands listed in Table 3-6. For a complete list of deprecated commands, see "Deprecated Commands for Oracle Infrastructure Web Services" in Release Notes.
Use the WLST commands listed in Table 3-6 to manage Oracle Infrastructure and RESTful Web Services direct and global policy attachments.
Table 3-6 Oracle Infrastructure and RESTful Web Services and Clients - WLST Commands for Direct Policy Attachments
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Attach a policy to the selected policy subject or policy set document within a session. |
Online |
|
|
Attach multiple policies to the selected policy subject or policy set document within a session. |
Online |
|
|
Detach a policy from the selected policy subject or policy set document within a session. |
Online |
|
|
Detach multiple policies from the selected policy subject or policy set document within a session. |
Online |
|
|
Enable or disable multiple policies that are attached to the selected policy subject or policy set document within a session. |
Online |
|
|
Enable or disable a policy that is attached to the selected policy subject or policy set document within a session. |
Online |
|
|
Display a list of all the available OWSM policies by category or subject type. |
Online |
|
|
List Web service client port policies information for an application. |
Online |
|
|
List Web service port policy information for a Web service in an application. |
Online |
|
|
Configure override properties for a policy that is attached to the selected policy subject or policy set document within a session. |
Online |
Use the WLST commands listed in Table 3-7 to manage Java EE Web Services (or clients) directly attached policies.
Table 3-7 Java EE Web Services (or Clients) - WLST Commands for Direct Policy Attachments
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Attach multiple policies to a Web service client port of an application. |
Online |
|
|
Attach an OWSM policy to a Web service client port of an application. |
Online |
|
|
Attach multiple policies to a Web service port of an application. |
Online |
|
|
Attach a policy to a Web service port of an application. |
Online |
|
|
Detach multiple policies from a Web service client port of an application. |
Online |
|
|
Detach a policy from a Web service client port of an application. |
Online |
|
|
Detach multiple OWSM policies from a Web service port of an application |
Online |
|
|
Detach an OWSM policy from a Web service port of an application. |
Online |
|
|
Enable or disable multiple policies of a Web service client port of an application. |
Online |
|
|
Enable or disable a policy of a Web service client port of an application. |
Online |
|
|
Enable or disable multiple policies attached to a port of a Web service application. |
Online |
|
|
Enable or disable a policy attached to a port of a Web service application. |
Online |
|
|
Display a list of all the available OWSM policies by category or subject type. |
Online |
|
|
List Web service client port policies information for an application. |
Online |
|
|
List Web service port policy information for a Web service in an application. |
Online |
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web services.
For Oracle Infrastructure Web Services, this command has been deprecated. It is recommended that you use the attachWSMPolicies command, as described in "attachWSMPolicies". The following examples show how to migrate to use the attachWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig>attachWebServiceClientPolicies ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort',["oracle/wss_username_token_client_policy","oracle/log_policy"])
12c Release:
wls:/wls-domain/serverConfig>attachWSMPolicies(["oracle/wss_username_token_client_policy","oracle/log_policy"])
Command Category: Policy Management
Use with WLST: Online
Attaches multiple policies to a Web service client port of an application.
The policyURIs are validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available.
For Java EE (wls) module types only: If the policies that you specify in this command are already attached or exist, then this command enables the policies that are already attached (if they are disabled), and attaches the others.
If the wsm-pm application is not installed or is not available, this command is not executed.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
attachWebServiceClientPolicies(application,moduleOrCompName,moduleType, serviceRefName,portInfoName,policyURIs,[subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to attach OWSM client policies to the Web service client port. For example, To attach policies to a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to attach the policies to the client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The client port to which you want to attach the OWSM client policy. |
|
|
The OWSM policy name URIs, for example, If the policies that you specify in this command are already attached or exist, then this command enables the policies that are already attached (if they are disabled), and attaches the others. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example attaches the policies oracle/wss10_saml20_token_client_policy and oracle/wss11_message_protection_client_policy to the client port UpperCaseImplPort in the Java EE Web module owsm_mbean.resouce_pattern.web.ClientJWS/sei2.
wls:/wls-domain/serverConfig>attachWebServiceClientPolicies ('/wls-domain/AdminServer/ClientJWS','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','wls','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','UpperCaseImplPort',["oracle/wss10_saml20_token_client_policy","oracle/wss11_message_protection_client_policy"])
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the attachWSMPolicy command, as described in "attachWSMPolicy". The following examples show how to migrate to use the attachWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig>attachWebServiceClientPolicy ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort',"oracle/wss_username_token_client_policy")
12c:
wls:/wls-domain/serverConfig>attachWSMPolicy("oracle/wss_username_token_client_policy")
Command Category: Policy Management
Use with WLST: Online
Attaches an OWSM policy to a Web service client port of an application.
The policyURI is validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available.
For Java EE (wls) module types only: If the PolicyURI that you specify in this command already is attached or exists, then this command enables the policy if it is disabled.
If the wsm-pm application is not installed or is not available, this command is not executed.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
attachWebServiceClientPolicy(application,moduleOrCompName,moduleType, serviceRefName, portInfoName, policyURI, [subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to attach a policy to the Web service client port. For example, To attach a policy to a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to attach the policy to the client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The client port to which you want to attach the OWSM client policy. |
|
|
The OWSM policy name URI, for example, If the policy that you specify is already attached or exists, then this command enables the policy if it is disabled. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example attaches the oracle/wss_username_token_client_policy client policy to the Java EE Web service client port UpperCaseImplPort of the Web module owsm_mbean.resouce_pattern.web.ClientJWS/sei2. The Web service is part of the application ClientJWS.
wls:/wls-domain/serverConfig> attachWebServiceClientPolicy ('/wls-domain/AdminServer/ClientJWS','owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'wls','owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'UpperCaseImplPort', "oracle/wss_username_token_client_policy")
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the attachWSMPolicies command, as described in "attachWSMPolicies". The following examples show how to migrate to use the attachWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig> attachWebServicePolicies ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort', ["oracle/log_policy", "oracle/wss_username_token_service_policy"])
12c Release:
wls:/wls-domain/serverConfig> attachWSMPolicies["oracle/log_policy", "oracle/wss_username_token_service_policy"])
Command Category: Policy Management
Use with WLST: Online
Attaches multiple policies to a Web service port of an application.
The policyURIs are validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available.
For Java EE (wls) module types only: if any of the policies that you specify in this command are already attached or exist, then this command enables the policies that are already attached (if they are disabled), and attaches the others.
If the wsm-pm application is not installed or is not available, this command is not executed.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
attachWebServicePolicies(application, moduleOrCompName, moduleType, serviceName, subjectName,policyURIs,[subjectType=None])
| Argument | Definition |
|---|---|
|
|
Name and path of the application to which you want to attach the Web service policies. For example, To attach the policies to a port of a Web service application, this argument is required. |
|
|
Name of the Web module to which you want to attach Web service policies. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application. For example, {http://namespace/}serviceName. |
|
|
Name of the policy subject, port, or operation. |
|
|
List of OWSM policy name URIs, for example, If any of the policies that you specify are already attached or exist, then this command enables the policies that are already attached (if they are disabled), and attaches the others. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example attaches the policies 'oracle/binding_authorization_denyall_policy', 'oracle/wss_username_token_service_policy' to the port helloWorldJaxwsSoapHttpPort of the Web module helloWorldJaxws. The Java EE Web service is part of the application helloWorldJaxws for the server AdminServer in the domain wls-domain.
wls:wls-domain/ServerConfig>attachWebServicePolicies ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort, ['oracle/binding_authorization_denyall_policy', 'oracle/wss_username_token_service_policy'])
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the attachWSMPolicy command, as described in "attachWSMPolicy". The following examples show how to migrate to use the attachWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig> attachWebServicePolicy ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort','oracle/wss_username_token_service_policy')
12c Release:
wls:/wls-domain/serverConfig> attachWSMPolicy('oracle/wss_username_token_service_policy')
Command Category: Policy Management
Use with WLST: Online
Attaches a policy to a Web service port of an application.
The policyURI is validated through the OWSM Policy Manager APIs if the wsm-pm application is installed on WebLogic Server and is available.
For Java EE (wls) module types only: If the PolicyURI that you specify in this command already is attached or exists, then this command enables the policy if it is disabled.
If the wsm-pm application is not installed or is not available, this command is not executed.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
attachWebServicePolicy(application, moduleOrCompName, moduleType, serviceName, subjectName, policyURI, [subjectType=None])
| Argument | Definition |
|---|---|
|
|
Name and path of the application to which you want to attach a Web service policy. For example, To attach a policy to a port of a Web service application, this argument is required. |
|
|
Name of the Web module to which you want to attach a Web service policy. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application. For example, |
|
|
Name of the policy subject, port, or operation. |
|
|
OWSM policy name URI, for example, |
|
|
Optional. Policy subject type. Valid options are:
|
The following example attaches the policy oracle/wss_username_token_service_policy to the port helloWorldJaxwsSoapHttpPort of the Java EE Web service helloWorldJaxws.
wls:wls-domain/serverConfig> attachWebServicePolicy ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort', 'oracle/wss_username_token_service_policy')
A Web service cannot contain both a WebLogic Web service policy and an Oracle Web service policy. If you have a Web service with a WebLogic Web service policy, you must first detach it before attaching the Oracle Web service policy. The following example detaches the WebLogic Web service policy Wssp1.2-2007-Saml2.0-SenderVouches-Wss1.1.xml from the port SimplePort in the Java EE Web service SimpleEjbService and then attaches the Oracle Web service policy oracle/wss_username_token_service_policy.
wls:wls-domain/serverConfig>detachWebServicePolicy('/wls-domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleEjbService', 'wls','SimpleEjbService', 'SimplePort','policy:Wssp1.2-2007-Saml2.0-SenderVouches-Wss1.1.xml') wls:wls-domain/serverConfig>attachWebServicePolicy('/wls-domain/AdminServer/SimpleJAXWS','SimpleJAXWS#1!SimpleEjbService', 'wls','SimpleEjbService', 'SimplePort', 'oracle/wss_username_token_service_policy')
Note:
The detachWebServicePolicy WLST command allows you to detach WebLogic Web service policies from a Web service. However, you cannot use the attachWebServicePolicy WLST command to attach WebLogic Web service policies. To attach WebLogic Web service policies to a Web service, you must use the WebLogic Administration Console.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, attaches multiple policies, identified by specified the URIs, to the selected policy subject.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. However, if attachWSMPolicies is issued when creating or cloning a policy set, there is no need to select the policy set because it is already selected. If there is no current session and no policy subject selected, an error is displayed.
attachWSMPolicies(uris)
| Element | Description |
|---|---|
|
|
List of OWSM policy name URIs, for example, |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, attaches a policy, identified by the specified URI, to the selected policy subject or policy set.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. However, if attachWSMPolicy is issued when creating or cloning a policy set, there is no need to select the policy set because it is already selected. If there is no current session and no policy subject is selected, an error is displayed.
attachWSMPolicy(uri)
| Argument | Definition |
|---|---|
|
|
OWSM policy name URI, for example, |
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the detachWSMPolicies command, as described in "detachWSMPolicies". The following examples show how to migrate to use the detachWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig>detachWebServiceClientPolicies ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort', ["oracle/log_policy","oracle/wss_username_token_client_policy"])
12c Release:
wls:/wls-domain/serverConfig>detachWSMPolicies(["oracle/log_policy","oracle/wss_username_token_client_policy"])
Command Category: Policy Management
Use with WLST: Online
Detaches multiple policies from a Web service client port of an application.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
detachWebServiceClientPolicies(application,moduleOrCompName,moduleType, serviceRefName,portInfoName,policyURIs,[subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to detach multiple policies from a Web service client port. For example, To detach multiple policies from a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to detach multiple policies from a client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The client port from which you want to detach the OWSM client policy. |
|
|
The OWSM policy name URI, for example, If the policy specified is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example detaches the client policies oracle/wss10_saml20_token_client_policy and oracle/wss11_message_protection_client_policy of the port UpperCaseImplPort of the Java EE Web service module owsm_mbean.resouce_pattern.web.ClientJWS/sei2.
wls:/wls-domain/serverConfig>detachWebServiceClientPolicies('/wls-domain/AdminServer/ClientJWS','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','wls','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','UpperCaseImplPort',["oracle/wss10_saml20_token_client_policy","oracle/wss11_message_protection_client_policy"])
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the detachWSMPolicy command, as described in "detachWSMPolicy". The following examples show how to migrate to use the detachWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig>detachWebServiceClientPolicy ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort','oracle/wss_username_token_client_policy')
12c Release:
wls:/wls-domain/serverConfig>detachWSMPolicy('oracle/wss_username_token_client_policy')
Command Category: Policy Management
Use with WLST: Online
Detaches a policy from a Web service client port of an application.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
detachWebServiceClientPolicy(application,moduleOrCompName,moduleType, serviceRefName, portInfoName, policyURI, [subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to detach a policy from a Web service client port. For example, To detach a policy from a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to detach the policy from a client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The client port from which you want to detach the OWSM client policy. |
|
|
The OWSM policy name URI, for example, If the policy specified is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Optional. Policy subject type. Valid options are:
|
The following command detaches the client policy oracle/wss_username_token_client_policy from the client port UpperCaseImplPort in the Java EE client module wsm_mbean.resouce_pattern.web.ClientJWS/sei2.
wls:/wls-domain/serverConfig> detachWebServiceClientPolicy('/wls-domain/AdminServer/ClientJWS', 'owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'wls', 'owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'UpperCaseImplPort', "oracle/wss_username_token_client_policy")
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the detachWSMPolicies command, as described in "detachWSMPolicies". The following examples show how to migrate to use the detachWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig>detachWebServicePolicies ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort', ["oracle/log_policy","oracle/wss_username_token_service_policy"])
12c Release:
wls:/wls-domain/serverConfig>detachWSMPolicies(["oracle/log_policy","oracle/wss_username_token_service_policy"])
Command Category: Policy Management
Use with WLST: Online
Detaches multiple OWSM policies from a Web service port of an application.
If the wsm-pm application is not installed or is not available, this command is not executed.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
detachWebServicePolicies(application, moduleOrCompName, moduleType, serviceName, subjectName, policyURIs,[subjectType=None])
| Argument | Definition |
|---|---|
|
|
Name and path of the application from which you want to detach the Web service policies. For example, To detach policies from a port of a Web service application, this argument is required. |
|
|
Name of the Web module from which you want to detach the Web service policies. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application. For example, {http://namespace/}serviceName. |
|
|
Name of the policy subject, port, or operation. |
|
|
List of OWSM policy name URIs, for example, If a policyURI specified is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example detaches the policies "oracle/binding_authorization_denyall_policy", "oracle/wss_username_token_service_policy" from the port helloWorldJaxwsSoapHttpPort of the Java EE Web module helloWorldJaxws. The Web service is part of the application helloWorldJaxws for the server AdminServer in the domain wls-domain.
wls:/wls-domain/serverConfig>detachWebServicePolicies ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort', ["oracle/binding_authorization_denyall_policy", "oracle/wss_username_token_service_policy"])
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the detachWSMPolicy command, as described in "detachWSMPolicy". The following examples show how to migrate to use the detachWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig>detachWebServicePolicy('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web','{http://namespace/}WssUsernameService','JRFWssUsernamePort','oracle/wss_username_token_service_policy')
12c Release:
wls:/wls-domain/serverConfig>detachWSMPolicy('oracle/wss_username_token_service_policy')
Command Category: Policy Management
Use with WLST: Online
Detaches an OWSM policy from a Web service port of an application.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
detachWebServicePolicy(application, moduleOrCompName, moduleType, serviceName, subjectName, policyURI, [subjectType=None])
| Argument | Definition |
|---|---|
|
|
Name and path of the application from which you want to detach a Web service policy. For example, To detach a policy from a port of a Web service application, this argument is required. |
|
|
Name of the Web module from which you want to detach a Web service policy. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application. For example, {http://namespace/}serviceName. |
|
|
Name of the policy subject, port, or operation. |
|
|
OWSM policy name URI, for example, If the policy specified is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example detaches the policy oracle/wss_username_token_service_policy from the port helloWorldJaxwsSoapHttpPort of the service helloWorldJaxws in the Java EE Web service wls-domain/AdminServer/helloWorldJaxws.
wls:/wls-domain/serverConfig>detachWebServicePolicy ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort', 'oracle/wss_username_token_service_policy')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, detaches multiple policies, identified by an array of URIs or index values, from the selected policy subject.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. If there is no current session and no policy subject selected, an error is displayed.
detachWSMPolicies(uris)
| Argument | Definition |
|---|---|
|
|
Array of URIs or index values specifying the policies to detach from a policy subject. For example, If the specified policy URIs are not attached, an error message is displayed and/or an exception is thrown. |
The following example detaches the OWSM logging policy and username token service policy from the current policy subject:
wls:/wls-domain/serverConfig>detachWSMPolicies(["oracle/log_policy","oracle/wss_username_token_service_policy"])
The following example uses the index values of the OWSM logging policy and username token service URIs to detach them from the current policy subject
wls:/wls-domain/serverConfig>detachWSMPolicies('1','3')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, detaches a policy, identified by the specified URI or index value, from the selected policy subject.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. If there is no current session and no policy subject selected, an error is displayed
Issuing this command outside of a session containing a policy subject that is being created or modified will result in an error.
detachWSMPolicy(uri)
| Argument | Definition |
|---|---|
|
|
URI or index value specifying the policy to detach from a policy subject. For example, If the specified policy URI is not attached, an error message is displayed and/or an exception is thrown. |
The following example detaches the OWSM logging policy from the current policy subject.
wls:/wls-domain/serverConfig>detachWSMPolicy('oracle/log_policy')
The following example uses the index value of the OWSM logging policy's URI to detach it from the current policy subject.
wls:/wls-domain/serverConfig>detachWSMPolicy('1')
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicies command, as described in "enableWSMPolicies". The following examples show how to migrate to use the enableWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig>enableWebServiceClientPolicies ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort', ["oracle/log_policy", "oracle/wss_username_token_client_policy"], true )
12c Release:
wls:/wls-domain/serverConfig>enableWSMPolicies(["oracle/log_policy", "oracle/wss_username_token_client_policy"], true )
Command Category: Policy Management
Use with WLST: Online
Enables or disables multiple policies of a Web service client port of an application.
Note:
Policy changes made using this WLST command are only effective after you restart your application
enableWebServiceClientPolicies(application,moduleOrCompName,moduleType, serviceRefName,portInfoName,policyURIs,[enable],[subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to enable or disable multiple policies of a Web service client port. For example, To enable or disable multiple policies of a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to enable or disable multiple policies of a client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The name of the client port to which you want to attach the OWSM client policies. |
|
|
The list of OWSM policy name URIs, for example, |
|
|
Optional. Specifies whether to enable or disable the policies. Valid options are:
If you omit this argument, the policies are enabled. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example enables the client policies oracle/wss10_saml20_token_client_policy and oracle/wss11_message_protection_client_policy of the port UpperCaseImplPort of the Java EE Web service module owsm_mbean.resouce_pattern.web.ClientJWS/sei2.
wls:/wls-domain/serverConfig>enableWebServiceClientPolicies('/wls-domain/AdminServer/ClientJWS','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','wls','owsm_mbean.resouce_pattern.web.ClientJWS/sei2','UpperCaseImplPort',["oracle/wss10_saml20_token_client_policy","oracle/wss11_message_protection_client_policy"], true)
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicy command, as described in "enableWSMPolicy". The following examples show how to migrate to use the enableWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig>enableWebServiceClientPolicy ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort', "oracle/wss_username_token_client_policy",true)
12c Release:
wls:/wls-domain/serverConfig>enableWSMPolicy("oracle/wss_username_token_client_policy",true)
Command Category: Policy Management
Use with WLST: Online
Enables or disables a policy of a Web service client port of an application.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
enableWebServiceClientPolicy(application,moduleOrCompName,moduleType, serviceRefName,portInfoName,policyURI,[enable],[subjectType=None] )
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to enable or disable a policy of a Web service client port. For example, To enable or disable a policy of a client port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to enable or disable a policy of a client port. |
|
|
Module type. Valid options are:
Note: The |
|
|
The service reference name of the application. |
|
|
The name of the client port to which you want to attach the OWSM client policy. |
|
|
The OWSM policy name URI, for example, |
|
|
Optional. Specifies whether to enable or disable the policy. Valid options are:
If you omit this argument, the policy is enabled. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example disables the client policy oracle/wss_username_token_client_policy on the client port UpperCaseImplPort in the Java EE Web module owsm_mbean.resouce_pattern.web.ClientJWS/sei2.
wls:/wls-domain/serverConfig>enableWebServiceClientPolicy('/wls-domain/AdminServer/ClientJWS', 'owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'wls', 'owsm_mbean.resouce_pattern.web.ClientJWS/sei2', 'UpperCaseImplPort', "oracle/wss_username_token_client_policy", false)
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicies command, as described in "enableWSMPolicies". The following examples show how to migrate to use the enableWSMPolicies command.
11g Release:
wls:/wls-domain/serverConfig> enableWebServicePolicies ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort',["oracle/log_policy", "oracle/wss_username_token_service_policy"],true)
12c Release:
wls:/wls-domain/serverConfig> enableWSMPolicies(["oracle/log_policy","oracle/wss_username_token_service_policy"],true)
Command Category: Policy Management
Use with WLST: Online
Enables or disables multiple policies attached to a port of a Web service application.
If the policyURIs that you specify in this command are not attached to the port, an error message is displayed and/or an exception is thrown.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
enableWebServicePolicies(application, moduleOrCompName, moduleType, serviceName, subjectName, policyURIs,[enable],[subjectType=None] ))
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to enable the Web service policies. For example, To enable policies that are attached to a port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to enable Web service policies. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application.For example, { |
|
|
Name of the policy subject, port, or operation. |
|
|
List of OWSM policy name URIs, for example, If the |
|
|
Optional. Specifies whether to enable or disable the policies. Valid options are:
If you omit this argument, the policies are enabled. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example disables the policies ["oracle/binding_authorization_denyall_policy","oracle/wss_username_token_service_policy"] attached to the port helloWorldJaxwsSoapHttpPort of the Web module helloWorldJaxws#1!helloWorldJaxws. The Web service is part of the application helloWorldJaxws for the server AdminServer in the domain wls-domain.
wls:/wls-domain/serverConfig>enableWebServicePolicies ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort', ["oracle/binding_authorization_denyall_policy", "oracle/wss_username_token_service_policy"], false)
Note:
Use this command for Java EE Web Services (or clients) only. It has been deprecated for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicy command, as described in "enableWSMPolicy". The following examples show how to migrate to use the enableWSMPolicy command.
11g Release:
wls:/wls-domain/serverConfig>enableWebServicePolicy ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy','web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort',"oracle/wss_username_token_service_policy",true)
12c Release:
wls:/wls-domain/serverConfig>enableWSMPolicy("oracle/wss_username_token_service_policy",true)
Command Category: Policy Management
Use with WLST: Online
Enables or disables a policy attached to a port of a Web service application.
If the policy that you specify in this command is not attached to the port, an error message is displayed and/or an exception is thrown.
Note:
Policy changes made using this WLST command are only effective after you restart your application.
enableWebServicePolicy(application, moduleOrCompName, moduleType, serviceName, subjectName, policyURI, [enable], [subjectType=None] ))
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to enable a Web service policy. For example, To enable a policy that is attached to a port of a Web service application, this argument is required. |
|
|
Name of the Web module) for which you want to enable a Web service policy. |
|
|
Module type. Valid options are:
Note: The |
|
|
Name of the Web service in the application. For example, { |
|
|
Name of the policy subject, port, or operation. |
|
|
OWSM policy name URI, for example, If the policy that you specify is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Optional. Specifies whether to enable or disable the policy. Valid options are:
If you omit this argument, the policy is enabled. |
|
|
Optional. Policy subject type. Valid options are:
|
The following example disables the policy oracle/wss_username_token_service_policy attached to the port helloWorldJaxwsSoapHttpPort for the service helloWorldJaxws in the Java EE Web service wls-domain/AdminServer/helloWorldJaxws
wls:/wls-domain/domainRuntime> enableWebServicePolicy ('/wls-domain/AdminServer/helloWorldJaxws','helloWorldJaxws#1!helloWorldJaxws', 'wls','helloWorldJaxws', 'helloWorldJaxwsSoapHttpPort', 'oracle/wss_username_token_service_policy', false)
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, enables or disables multiple policy attachments, identified by the specified URIs, that are attached to a policy subject.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. However, if enableWSMPolicies is issued when creating or cloning a policy set, there is no need to select the policy set because it is already selected.
If the optional enable argument is not specified, this command enables the policy attachment by default. If the policy URIs that you specify in this command are not attached to the port, an error message is displayed and/or an exception is thrown.
enableWSMPolicies(uris,[enable=true]))
| Argument | Definition |
|---|---|
|
|
List of OWSM policy name URIs, for example, If the |
|
|
Optional. Specifies whether to enable or disable the policy attachments. Valid options are:
If you omit this argument, the policies are enabled. |
The following example enables the policies ["oracle/log_policy","oracle/wss_username_token_service_policy"] attached to the port JRFWssUsernamePort of the Web module WssUsernameService. The Web service is part of the application HelloWorld#1_0 for the server server1 in the domain base_domain.
wls:/wls-domain/serverConfig>enableWSMPolicies(["oracle/log_policy","oracle/wss_username_token_service_policy"],true)
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, enables or disables a policy attachment, identified by a specified URI, that is attached to a policy subject.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. However, if enableWSMPolicy is issued when creating or cloning a policy set, there is no need to select the policy set because it is already selected.
If the optional enable argument is not specified, this command enables the policy attachment by default. If the policyURIs that you specify in this command are not attached to the port, an error message is displayed and/or an exception is thrown.
enableWSMPolicy(uri,[enable=true])
| Argument | Definition |
|---|---|
|
|
URI specifying the policy attachment within the policy set. |
|
|
Optional. Specifies whether to enable or disable the policy attachment specified by the URI in the policy set. Valid options are:
If you omit this argument, the policy set attachment is enabled. |
The following example enables the policy oracle/wss_username_token_service_policy attached to the port JRFWssUsernamePort of the Web module WssUsernameService. The Web service is part of the application HelloWorld#1_0 for the server server1 in the domain base_domain.
wls:/wls-domain/serverConfig>enableWSMPolicy("oracle/wss_username_token_service_policy",true)
Command Category: Policy Management
Use with WLST: Online
listAvailableWebServicePolicies([category],[subject])
| Argument | Definition |
|---|---|
|
|
Optional. The policy category, for example,: |
|
|
Optional. The policy subject type, for example,: |
Command Category: Policy Management
Use with WLST: Online
Lists Web service client port policies information for an application.
The output will display the Web service client/reference port name, the OWSM policies it has attached to it and details about each attachment such as the policy category, status, the source of the policy attachment, any policy override properties (if applicable), and if the policy is in effect for the subject. It also displays if the policy subject is secure. For example:
test-port: URI=oracle/wss_username_token_client_policy, category=security, policy-status=enabled source=local policy set; reference-status=enabled; effective=true The policy subject is secure in this context.
listWebServiceClientPolicies(application, moduleOrCompName, moduleType, serviceRefName,portInfoName)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web service client port policy information. For example, To list the client port policy information for a Web services application, this argument is required. |
|
|
Name of the Web module) for which you want to list the Web services port policy information. |
|
|
Module type. Valid options are:
|
|
|
The service reference name of the application. |
|
|
The client port name. |
The following example lists the Web service client port policy information for the application jwsclient_1#1.1.0 for the server server1 in the domain base_domain. In this example, the Web module name is WssUsernameClient, the module type is wsconn, the service reference name is WssUsernameClient, and the client port name is JRFWssUsernamePort.
wls:/wls-domain/serverConfig>listWebServiceClientPolicies ('/base_domain/server1/jwsclient_1#1.1.0','WssUsernameClient','wsconn', 'WssUsernameClient','JRFWssUsernamePort')
Command Category: Policy Management
Use with WLST: Online
Lists Web service policy information for a Web service port in an application.
The output will display the Web service port name, the OWSM policies it has attached to it and details about each attachment such as the policy category, status, the source of the policy attachment, any policy override properties (if applicable), and if the policy is in effect for the subject. It also displays if the policy subject is secure. For example:
CalculatorPort: URI="oracle/wss_username_token_service_policy", category=security, policy-status=enabled; source=local policy set; reference-status=enabled; effective=true The policy subject is secure in this context.
listWebServicePolicies(application,moduleOrCompName,moduleType,serviceName,subjectName)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to list the Web services port policy information. For example, To list the port policy information for a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to list the Web services port policy information. |
|
|
Module type. Valid options are:
|
|
|
Name of the Web service in the application for which you want to list the port policy information. For example, { |
|
|
Policy subject, port, or operation name. |
The following example lists the Web service policy information for the port CalculatorPort in the application jaxwsejb30ws. In this example, the Web module name is jaxwsejb, and the service name is CalculatorService.
wls:/wls-domain/serverConfig>listWebServicePolicies ('/base_domain/AdminServer/jaxwsejb30ws','jaxwsejb','web', '{http://namespace/}CalculatorService', 'CalculatorPort')
Note:
This command has been deprecated for Oracle Infrastructure Web Services. It is recommended that you use the setWSMPolicyOverride command, as described in "setWSMPolicyOverride".
This command does not apply to Java EE Web services.
The following examples show how to migrate to use the setWSMPolicyOverride command.
11g Release:
wls:/jrfServer_domain/serverConfig> setWebServicePolicyOverride ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy', 'web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort', 'oracle/wss_username_token_service_policy', 'reference.priority', '10')
12c Release (for repository and policy subject operations):
wls:/jrfServer_domain/serverConfig> setWSMPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')
Command Category: Policy Management
Use with WLST: Online
setWebServicePolicyOverride(application,moduleOrCompName,moduleType, serviceName, portName,policyURI,properties)
| Argument | Definition |
|---|---|
|
|
Name and path of the application for which you want to override the Web service port policy. For example, To override properties on a policy attached to a port of a Web service application, this argument is required. |
|
|
Name of the Web module for which you want to override a Web service port policy. |
|
|
Module type. The valid option is Note: The module type |
|
|
Name of the Web service in the application. For example, { |
|
|
Name of the policy subject, port, or operation. |
|
|
OWSM policy name URI, for example, If the policy specified is not attached, an error message is displayed and/or an exception is thrown. |
|
|
Policy override properties. Properties must be specified using the following format:
For example: If this argument is set to |
The following example configures the override properties for the policy oracle/wss10_message_protection_service_policy for the port JRFWssUsernamePort of the Web module WssUsernameService. The Web service is part of the application HelloWorld#1_0 for the server server1 in the domain base_domain.
wls:/wls-domain/serverConfig>setWebServicePolicyOverride ('/base_domain/server1/HelloWorld#1_0','j2wbasicPolicy', 'web', '{http://namespace/}WssUsernameService','JRFWssUsernamePort', "oracle/wss10_message_protection_service_policy", [("keystore.sig.csf.key","sigkey")])
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Management
Use with WLST: Online
Within a session, adds a configuration override, described by a name-value pair, to a policy identified by the specified URI and attached to the policy set document or policy subject. The value argument is optional. If the value argument is omitted, the property specified by the name argument is removed from the policy subject. If the property specified by the name argument already exists and a value argument is provided, the current value is overwritten by the new value.
You must start a session and select the policy set (selectWSMPolicySet) or policy subject (selectWSMPolicySubject) before initiating the command. If there is no current session and no policy subject selected, an error is displayed.
setWSMPolicyOverride(uri, name, value)
| Argument | Description |
|---|---|
|
|
String representing the policy URI. For example, |
|
|
String representing the name of the override property. For example: |
|
|
Optional. String representing the value of the property. If this argument is not specified, the property specified by the |
The following example specifies a configuration override for the reference.priority property for the oracle/wss10_saml_token_service_policy to a value of 1.
wls:/wls-domain/serverConfig> setWSMPolicyOverride('oracle/wss10_saml_token_service_policy', 'reference.priority','1')
The following example removes the property reference.priority from the oracle/wss10_saml_token_service_policy in the policy set.
wls:/wls-domain/serverConfig> setWSMPolicyOverride('oracle/wss10_saml_token_service_policy', 'reference.priority')
Policy sets enhance the security and manageability of an enterprise by providing a mechanism to globally attach one or more policies to a subject type. Using policy sets, an administrator can specify a default set of policies to be enforced even if none are directly attached. For detailed information about determining the type and scope of resources a policy set can be attached to, see "Defining the Type and Scope of Resources for Globally Attached Policies" in the Securing Web Services and Managing Policies with Oracle Web Services Manager.
All policy set creation, modification, or deletion commands must be performed in the context of a session. A session can only act on a single policy set.
Notes:
The procedures in this section apply to Oracle Infrastructure and RESTful Web Services only. To view the help for the WLST commands described in this section, connect to a running instance of the server and enter help('wsmManage').
The policy set management commands listed in Table 3-9 have been deprecated in this release for Oracle Infrastructure Web Services.
For Oracle Infrastructure Web Services, Oracle recommends that you use the new WLST commands listed in Table 3-8 to manage OWSM policy sets in release 12c. These commands must be executed within the context of a session using the session commands described in Session Commands.
For a complete list of deprecated commands, see "Deprecated Commands for Oracle Infrastructure Web Services" in Release Notes.
Use the WLST commands listed in Table 3-6 to manage Oracle Infrastructure and RESTful Web Services globally available policy sets.
Table 3-8 Oracle Infrastructure Web Services Global Policy Set Management WLST Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Within a session, clone a new policy set from an existing policy set. |
Online |
|
|
Create a new, empty policy set within a session. |
Online |
|
|
Delete all or selected policy sets from within the OWSM repository. |
Online |
|
|
Delete a specified policy set within a session. |
Online |
|
|
Display the configuration of a specified policy set. |
Online |
|
|
Enable or disable the current policy set within a session. |
Online |
|
|
Lists the policy sets in the repository. This command will also display a policy set that is being created, modified, or deleted within the current session. |
Online |
|
|
Specify a policy set for modification within a session. |
Online |
|
|
Specify a run-time constraint value for a policy set selected within a session. |
Online |
|
|
Configure override properties to a policy set. |
Online |
|
|
Specify a description for a policy set selected within a session. |
Online |
|
|
Set an expression that attaches a policy set to the specified resource scope. |
Online |
|
|
Validate an existing policy set. |
Online |
Table 3-9 list the WLST commands that are deprecated in this release for managing Oracle Infrastructure Web service global policy sets.
Table 3-9 Deprecated WLST Commands for Global Policy Set Management
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Abort the current OWSM repository modification session, discarding any changes that were made to the repository during the session. |
Online |
|
|
Attach a policy set to the specified resource scope. |
Online |
|
|
Attach a policy to a policy set using the policy's URI. |
Online |
|
|
Begin a session to modify the OWSM repository. |
Online |
|
|
Clone a new policy set from an existing policy set. |
Online |
|
|
Write the contents of the current session to the OWSM repository. |
Online |
|
|
Create a new, empty policy set. |
Online |
|
|
Delete all or selected policy sets from within the OWSM repository. |
Online |
|
|
Delete a specified policy set. |
Online |
|
|
Describe the contents of the current session. |
Online |
|
|
Detach a policy from a policy set using the policy's URI. |
Online |
|
|
Display the configuration of a specified policy set. |
Online |
|
|
Enable or disable a policy set. |
Online |
|
|
Enable or disable a policy attachment for a policy set using the policy's URI. |
Online |
|
|
List the policy sets in the repository. |
Online |
|
|
Migrate direct policy attachments to global policy attachments if they are identical. |
Online |
|
|
Specify an existing policy set for modification in the current session. |
Online |
|
|
Specify a run-time constraint value for a policy set selected within a session. |
Online |
|
|
Specify a description for the policy set selected within a session. |
Online |
|
|
Add a configuration override to a policy reference in the current policy set. |
Online |
|
|
Validate an existing policy set in the repository or in a session. |
Online |
Note:
This command has been deprecated. It is recommended that you use the abortWSMSession command, as described in "abortWSMSession".
The following examples show how to migrate to use the abortWSMSession command.
11g Release (for Repository operations):
wls:/jrfServer_domain/serverConfig> abortRepositorySession()
12c Release (for both Repository and PolicySubject operations):
wls:/jrfServer_domain/serverConfig> abortWSMSession()
Command Category: Policy Set Management
Use with WLST: Online
Aborts the current modification session, discarding any changes that were made to the repository during the session.
Note:
This command has been deprecated. It is recommended that you use the setWSMPolicySetScope command, as described in "setWSMPolicySetScope".
The following examples show how to migrate to use the setWSMPolicySetScope command.
11g Release:
wls:/jrfServer_domain/serverConfig> attachPolicySet ('Domain("base_domain")')
12c Release:
wls:/jrfServer_domain/serverConfig> setWSMPolicySetScope ('Domain("base_domain")')
Command Category: Policy Set Management
Use with WLST: Online
Within a session, sets an expression that attaches a policy set to the specified resource scope. The expression must define a valid resource scope in a supported format.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
attachPolicySet(expression)
| Argument | Definition |
|---|---|
|
|
Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. |
The following example attaches a policy set to the specified base_domain resource.
wls:/wls-domain/serverConfig>attachPolicySet('Domain("base_domain")')
This example attaches a policy set to the specified base_domain and managed_server resources.
wls:/wls-domain/serverConfig>attachPolicySet('Domain("base_domain") and Server("managed_server")')
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the attachWSMPolicy command, as described in "attachWSMPolicy". The following examples show how to migrate to use the attachWSMPolicy command.
11g Release (for both Repository and PolicySubject operation on policy set):
wls:/jrfServer_domain/serverConfig> attachPolicySetPolicy ('oracle/wss_username_token_service_policy')
12c Release:
wls:/jrfServer_domain/serverConfig> attachWSMPolicy('oracle/wss_username_token_service_policy')
Command Category: Policy Set Management
Use with WLST: Online
Within a session, attaches a policy, identified by the specified URI, to the current policy set.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
attachPolicySetPolicy(uri)
| Argument | Definition |
|---|---|
|
|
URI specifying the policy to attach to the current policy set. For example, |
Note:
This command has been deprecated. It is recommended that you use the beginWSMSession command, as described in "beginWSMSession".
The following examples show how to migrate to use the beginWSMSession command.
11g Release (for Repository operations):
wls:/jrfServer_domain/serverConfig> beginRepositorySession()
12c Release (for both Repository and PolicySubject operations):
wls:/jrfServer_domain/serverConfig> beginWSMSession()
Command Category: Policy Set Management
Use with WLST: Online
Begins a session to modify the OWSM Repository. A session can only act on a single policy subject, such as a policy set or a Fusion Middleware Web service endpoint. An error will be displayed if there is already a current session.
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the cloneWSMPolicySet command, as described in "cloneWSMPolicySet". The following examples show how to migrate to use the cloneWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> clonePolicySet ('myNewPolicySet', 'myPolicySet')
12c Release:
wls:/jrfServer_domain/serverConfig> cloneWSMPolicySet ('myNewPolicySet', 'myPolicySet')
Command Category: Policy Set Management
Use with WLST: Online
Within a session, clones a new policy set from an existing policy set. When cloning an existing policy set, all values and attachments in the source policy set are copied into the new policy set, although you can supply a different expression identifying the resource scope. The expression must define a valid resource scope in a supported format.
Issuing this command outside of a session will result in an error.
clonePolicySet(name, source,[attachTo=None],[description=None],[enable='true'])
| Argument | Definition |
|---|---|
|
|
Name of the new policy set clone. |
|
|
Name of the source policy set that will be cloned. |
|
|
Optional. Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. If this argument is set to |
|
|
Optional. Description for the new policy set. If this argument is set to |
|
|
Optional. Specifies whether to enable or disable the policy set. Valid options are:
If you omit this argument, the policy set is enabled. |
The first example creates a policy set by cloning the existing myPolicySet policy set to create a new mynewPolicySet. The second example also creates a policy set, but narrows the resource scope to policy subjects in the specified jaxwsejb30ws application in the domain.
wls:/wls-domain/serverConfig>clonePolicySet('myNewPolicySet','myPolicySet') wls:/wls-domain/serverConfig>clonePolicySet('myNewPolicySet','myPolicySet','Application("jaxwsejb30ws")')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, clones a new policy set from an existing policy set. When cloning an existing policy set, all values and attachments in the source policy set are copied into the new policy set, although you can supply a different expression identifying the resource scope. The expression must define a valid resource scope in a supported format.
Issuing this command outside of a session will result in an error.
cloneWSMPolicySet(name,source,[scope=None],[description=None],[enable='true'])
| Argument | Definition |
|---|---|
|
|
Name of the new policy set clone. |
|
|
Name of the source policy set that will be cloned. |
|
|
Optional. Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. If this argument is not specified, then the expression used in the source policy set to identify the scope of resources is retained. |
|
|
Optional. Description for the new policy set. If this argument is not specified, then the description used in the source policy set is retained. |
|
|
Optional. Specifies whether to enable or disable the policy set. If you omit this argument, the policy set is enabled.Valid options are:
If you omit this argument, the policy set is enabled. |
The first example creates a policy set by cloning the existing myPolicySet policy set to create a new mynewPolicySet. The second example also creates a policy set, but narrows the resource scope to policy subjects in the specified jaxwsejb30ws application in the domain.
wls:/wls-domain/serverConfig>cloneWSMPolicySet('myNewPolicySet','myPolicySet') wls:/wls-domain/serverConfig>cloneWSMPolicySet('myNewPolicySet','myPolicySet','Application("jaxwsejb30ws")')
Note:
This command has been deprecated. It is recommended that you use the commitWSMSession command, as described in "commitWSMSession".
The following examples show how to migrate to use the commitWSMSession command.
11g Release (for Repository operations):
wls:/jrfServer_domain/serverConfig> commitRepositorySession()
12c Release (for both Repository and PolicySubject operations):
wls:/jrfServer_domain/serverConfig> commitWSMSession()
Command Category: Policy Set Management
Use with WLST: Online
Writes the contents of the current session to the OWSM Repository. Messages are displayed that describe what was committed. An error will be displayed if there is no current session.
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the createWSMPolicySet command, as described in "createWSMPolicySet". The following examples show how to migrate to use the createWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> createPolicySet('myPolicySet', 'ws-service', 'Domain("base_domain")')
12c Release:
wls:/jrfServer_domain/serverConfig> createWSMPolicySet ('myPolicySet', 'ws-service', 'Domain("base_domain")')
Command Category: Policy Set Management
Use with WLST: Online
Creates a new, empty policy set within a session. When creating a new policy set, you must specify the type of policy subject that the policy set will apply to, and a supported expression that defines a valid resource scope in a supported format.
Issuing this command outside of a session will result in an error.
createPolicySet(name,type,attachTo,[description=None],[enable='true'])
| Argument | Definition |
|---|---|
|
|
Name of the new, empty policy set. |
|
|
The type of policy subject to which the new policy set applies. The type of policy subject must be one of the policy subjects described in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager. |
|
|
Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. |
|
|
Optional. Description of the new policy set. If no description is specified, then the description for a new policy set will be "Global policy attachments for |
|
|
Optional. Specifies whether to enable or disable the new policy set. Valid options are:
If you omit this argument, the policy set is enabled. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, creates a new, empty policy set. When creating a new policy set, you must specify the type of policy subject that the policy set will apply to, and provide a supported expression that defines a valid resource scope in a supported format.
Issuing this command outside of a session will result in an error.
createWSMPolicySet(name,type,scope,[description=None],[enable='true'])
| Argument | Definition |
|---|---|
|
|
Name of the new, empty policy set. |
|
|
The type of policy subject that the new policy set applies to. The type of policy subject must be one of the policy subjects described in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager. |
|
|
Optional. Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. If this argument is not specified, then the expression used in the source policy set to identify the scope of resources is retained. |
|
|
Optional. Description of the new policy set. If no description is specified, then the description for a new policy set will be "Global policy attachments for |
|
|
Optional. Specifies whether to enable or disable the new policy set. Valid options are:
If you omit this argument, the policy set is enabled. |
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the deleteWSMAllPolicySets command, as described in "deleteWSMAllPolicySets". The following examples show how to migrate to use the deleteWSMAllPolicySets command.
11g Release:
wls:/jrfServer_domain/serverConfig> deleteAllPolicySets()
12c Release:
wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets()
Command Category: Policy Set Management
Use with WLST: Online
Deletes all or selected policy sets from within the OWSM repository. You can specify whether to force deletion of all the policy sets, or prompt to select individual policy sets for deletion. If deletion of any policy set fails then this operation throws an exception and no policy sets are deleted.
deleteAllPolicySets([mode])
| Argument | Definition |
|---|---|
|
|
Optional. The action to be taken for performing policy set deletion. Valid options are:
If no mode is specified, this argument defaults to |
The following example automatically deletes all policy sets from the respository without prompting.
wls:/jrfServer_domain/serverConfig> deleteAllPolicySets("force")
Starting Operation deleteAllPolicySets ...
All policy sets were deleted successfully from repository.
deleteAllPolicySets Operation Completed.
The following examples delete selected policy sets from the repository.
wls:/jrfServer_domain/serverConfig> deleteAllPolicySets()
or
wls:/jrfServer_domain/serverConfig> deleteAllPolicySets('prompt')
Starting Operation deleteAllPolicySets ...
Policy Set Name: create_policyset_6
Select "create_policyset_6" for deletion (yes/no/cancel)? no
Policy Set Name: create_policyset_8
Select "create_policyset_8" for deletion (yes/no/cancel)? yes
Policy Set Name: create_policyset_21
Select "create_policyset_21" for deletion (yes/no/cancel)? no
Policy Set Name: create_policyset_10
Select "create_policyset_10" for deletion (yes/no/cancel)? yes
All the selected policy sets were deleted successfully from repository.
deleteAllPolicySets Operation Completed.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Deletes all or selected policy sets within a session. You can specify whether to force deletion of all the policy sets, or prompt to select individual policy sets for deletion. If deletion of any policy set fails then this operation throws an exception and no policy sets are deleted.
deleteWSMAllPolicySets([mode])
| Argument | Definition |
|---|---|
|
|
Optional. The action to be taken for performing policy set deletion. Valid options are:
If no mode is specified, this argument defaults to |
The following example automatically deletes all policy sets from the respository without prompting.
wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets("force")
Starting Operation deleteWSMAllPolicySets ...
All policy sets were deleted successfully from repository.
deleteWSMAllPolicySets Operation Completed.
The following examples delete selected policy sets from the repository.
wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets()
or
wls:/jrfServer_domain/serverConfig> deleteWSMAllPolicySets('prompt')
Starting Operation deleteWSMAllPolicySets ...
Policy Set Name: create_policyset_6
Select "create_policyset_6" for deletion (yes/no/cancel)? no
Policy Set Name: create_policyset_8
Select "create_policyset_8" for deletion (yes/no/cancel)? yes
Policy Set Name: create_policyset_21
Select "create_policyset_21" for deletion (yes/no/cancel)? no
Policy Set Name: create_policyset_10
Select "create_policyset_10" for deletion (yes/no/cancel)? yes
All the selected policy sets were deleted successfully from repository.
deleteWSMAllPolicySets Operation Completed.
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the deleteWSMPolicySet command, as described in "deleteWSMPolicySet". The following examples show how to migrate to use the deleteWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> deletePolicySet('myPolicySet')
12c Release:
wls:/jrfServer_domain/serverConfig> deleteWSMPolicySet ('myPolicySet')
Command Category: Policy Set Management
Use with WLST: Online
Deletes a specified policy set within a session. If the session already contains a different policy set, an error will display. If the session already contains the named policy set, then a creation will be undone or a modification will be converted into a deletion.
Issuing this command outside of a session will result in an error.
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, deletes a specified policy set. If the session already contains a different policy set, an error will display. If the session already contains the named policy set, then a creation will be undone or a modification will be converted into a deletion.
Issuing this command outside of a session will result in an error.
Note:
This command has been deprecated. It is recommended that you use the describeWSMSession command, as described in "describeWSMSession". The following examples show how to migrate to use the describeWSMSession command.
11g Release (for Repository operations):
wls:/jrfServer_domain/serverConfig> describeRepositorySession()
12c Release (for both Repository and Policy Subject operations):
wls:/jrfServer_domain/serverConfig> describeWSMSession()
Command Category: Policy Set Management
Use with WLST: Online
Describes the contents of the current session. This will either indicate that the session is empty or list the name of the policy subject that is being updated, along with the type of update (create, modify, or delete). An error will be displayed if there is no current session.
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the detachWSMPolicy command, as described in "detachWSMPolicy". The following examples show how to migrate to use the detachWSMPolicy command.
11g Release (for both Repository and Policy Subject operations on policy set):
wls:/jrfServer_domain/serverConfig> detachPolicySetPolicy ('oracle/wss_username_token_service_policy')
12c Release:
wls:/jrfServer_domain/serverConfig> detachWSMPolicy('oracle/wss_username_token_service_policy')
Command Category: Policy Set Management
Use with WLST: Online
Within a session, detaches a policy, identified by a specified URI, from the current policy set.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
detachPolicySetPolicy(uri)
| Argument | Definition |
|---|---|
|
|
URI specifying the policy to detach to the current policy set. For example, |
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the displayWSMPolicySet command, as described in "displayWSMPolicySet". The following examples show how to migrate to use the displayWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> displayPolicySet('myPolicySet')
12c Release:
wls:/jrfServer_domain/serverConfig> displayWSMPolicySet ('myPolicySet')
Command Category: Policy Set Management
Use with WLST: Online
Displays the configuration of a specified policy set. If the policy set is being modified in the current session, then that version will be displayed; otherwise, the latest version in the repository will be displayed. An error will display if the policy set does not exist.
This command can be issued outside of a session.
displayPolicySet([name])
| Argument | Definition |
|---|---|
|
|
Optional. Name of the policy set to be displayed. If a name is not specified, the configuration of the policy set, if any, in the current session is displayed or an error message is displayed. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Displays the configuration of a specified policy set. If the policy set is being modified in the current session, then that version will be displayed; otherwise, the latest version in the repository will be displayed. An error will display if the policy set does not exist.
This command can be issued outside of a session.
displayWSMPolicySet([name])
| Argument | Definition |
|---|---|
|
|
Optional. Name of the policy set to be displayed. If a name is not specified, the configuration of the policy set, if any, in the current session is displayed or an error message is displayed. |
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicySet command, as described in "enableWSMPolicySet". The following examples show how to migrate to use the enableWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> enablePolicySet(true)
12c Release:
wls:/jrfServer_domain/serverConfig> enableWSMPolicySet(true)
Command Category: Policy Set Management
Use with WLST: Online
Enables or disables the current policy set within a session. If not specified, this command enables the policy set.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
enablePolicySet([enable=True])
| Argument | Definition |
|---|---|
|
|
Optional. Specifies whether to enable or disable the policy set. Valid options are:
If you omit this argument, the policy set is enabled. |
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the enableWSMPolicySet command, as described in "enableWSMPolicySet". The following examples show how to migrate to use the enableWSMPolicySet command.
11g Release:
wls:/wls-domain/serverConfig>enablePolicySetPolicy('/oracle/log_policy',false)
12c Release:
wls:/wls-domain/serverConfig>enableWSMPolicy('/oracle/log_policy',false)
Command Category: Policy Set Management
Use with WLST: Online
Within a session, enables or disables the policy attachment, which is identified by the provided URI in the current policy set. If not specified, this command enables the policy set. An error displays if the identified policy is not currently attached to the policy set.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
enablePolicySetPolicy(uri,[enable=true])
| Argument | Definition |
|---|---|
|
|
URI specifying the policy attachment within the policy set. |
|
|
Optional. Specifies whether to enable or disable the policy attachment specified by the URI in the policy set. Valid options are:
If you omit this argument, the policy set attachment is enabled. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, enables or disables the current policy set. If the optional enable argument is not specified, this command enables the policy set by default.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
enableWSMPolicySet([enable=True])
| Argument | Definition |
|---|---|
|
|
Optional. Specifies whether to enable or disable the policy set. Valid options are:
If you omit this argument, the policy set is enabled. |
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the listWSMPolicySets command, as described in "listWSMPolicySets". The following examples show how to migrate to use the listWSMPolicySets command.
11g Release:
wls:/wls-domain/serverConfig>listPolicySets('ws-service')
12c Release:
wls:/wls-domain/serverConfig>listWSMPolicySets('ws-service')
Command Category: Policy Set Management
Use with WLST: Online
Lists the policy sets in the repository. This command will also display a policy set that is being created, modified, or deleted within the current session. You can list all the policy sets or limit the display to include only those that apply to specific policy subject resource types.
listPolicySets([type=None])
| Argument | Definition |
|---|---|
|
|
Optional. Specifies the type of policy subject for which the associated policy sets will be displayed. The type of policy subject must be one of the policy subjects described in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager If this argument is set to |
The first two examples list policy sets by either the ws-service or ws-client resource types. The third example lists all the policy sets stored in the repository.
wls:/wls-domain/serverConfig>listPolicySets('ws-service') wls:/wls-domain/serverConfig>listPolicySets('ws-client') wls:/wls-domain/serverConfig>listPolicySets()
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Lists the policy sets in the repository. This command will also display a policy set that is being created, modified, or deleted within the current session. You can list all the policy sets or use the type argument to limit the display to include only those sets that apply to specific policy subject resource types.
listWSMPolicySets([type=None])
| Argument | Definition |
|---|---|
|
|
Optional. Specifies the type of policy subject for which the associated policy sets will be displayed. The type of policy subject must be one of the policy subjects described in "Understanding Policy Subjects" in Understanding Oracle Web Services Manager. If this argument is set to |
The first two examples list policy sets by either the ws-service or ws-client resource types. Whereas, the third example lists all the policy sets stored in the repository.
wls:/wls-domain/serverConfig>listWSMPolicySets('ws-service') wls:/wls-domain/serverConfig>listWSMPolicySets('ws-client') wls:/wls-domain/serverConfig>listWSMPolicySets()
Note:
This command has been deprecated. It is recommended that you use the migrateWSMAttachments command, as described in "migrateWSMAttachments". The following examples show how to migrate to use the migrateWSMAttachments command.
11g Release:
wls:/jrfServer_domain/serverConfig> migrateAttachments()
12c Release:
wls:/jrfServer_domain/serverConfig> migrateWSMAttachments()
Command Category: Policy Set Management
Use with WLST: Online
Migrates direct (local) policy attachments that are identical to the external global policy attachments that would otherwise be attached to each policy subject in the current domain. You can specify whether to force the migration, prompt for confirmation before each migration, or simply list the migrations that would occur. A direct policy attachment is identical if its URI is the same as one provided by a global policy attachment, and if it does not have any scoped configuration overrides.
Note:
A direct attachment with an unscoped override will be migrated but an attachment with a scoped override will not. This is because after running the migrateAttachments() command, the enforcement of the policies on all subjects remains the same, even though some policies are globally attached.
Whether forced or prompted, the command lists each direct policy attachment that is migrated. This output will identify the policy subject that was modified, the URI of the identical policy reference, and the name of the global policy attachment document that duplicated the direct attachment.
migrateAttachments([mode])
| Argument | Definition |
|---|---|
|
|
The action to be taken for each policy attachment that can be migrated. Valid options are:
If no mode is specified, this argument defaults to |
The following examples describe how to use the repository attachment migration modes.
wls:/wls-domain/serverConfig>migrateAttachments() wls:/wls-domain/serverConfig>migrateAttachments('force') wls:/wls-domain/serverConfig>migrateAttachments('preview') wls:/wls-domain/serverConfig>migrateAttachments('prompt')
Note:
For Oracle Infrastructure Web Services, it is recommended that you use the selectWSMPolicySet command, as described in "selectWSMPolicySet". The following examples show how to migrate to use the selectWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> modifyPolicySet('myPolicySet')
12c Release:
wls:/jrfServer_domain/serverConfig> selectWSMPolicySet ('myPolicySet')
Command Category: Policy Set Management
Use with WLST: Online
Specifies a policy set for modification in the current session. The latest version of the named policy set will be loaded into the current session. If the session already contains a different policy set, then an error will be displayed; if the session already contains the named policy set, then no action will be taken. Subsequent attempts to modify the named policy set will show the current version in the session.
Issuing this command outside of a session will result in an error.
modifyPolicySet(name)
| Argument | Definition |
|---|---|
|
|
Name of the policy set to be modified in the current session. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, specifies a policy set for modification. The latest version of the named policy set is loaded into the current session. If the session already contains a different policy set, then an error will be displayed; if the session already contains the named policy set, then no action will be taken. Subsequent attempts to modify the named policy set will show the current version in the session.
Issuing this command outside of a session will result in an error.
selectWSMPolicySet(name)
| Argument | Description |
|---|---|
|
|
Name of the policy set to be modified in the current session. |
Note:
This command has been deprecated. It is recommended that you use the setWSMPolicySetConstraint command, as described in "setWSMPolicySetConstraint". The following examples show how to migrate to use the setWSMPolicySetConstraint command.
11g Release:
wls:/jrfServer_domain/serverConfig> setPolicySetConstraint ('HTTPHeader("VIRTUAL_HOST_TYPE","external")')
12c Release:
wls:/jrfServer_domain/serverConfig> setWSMPolicySetConstraint ('HTTPHeader("VIRTUAL_HOST_TYPE","external")')
Command Category: Policy Set Management
Use with WLST: Online
Specifies a run-time constraint value for a policy set selected within a session. Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
For more information, see "Specifying Run-time Constraints in Policy Sets" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
setPolicySetConstraint(constraint)
| Argument | Definition |
|---|---|
|
|
Expression that specifies the run-time context to which the policy set applies. If not specified, the policy set applies to all run-time contexts. |
The following example specifies that the policy set apply only to requests from external clients.
wls:/wls-domain/serverConfig> setPolicySetConstraint('HTTPHeader("VIRTUAL_HOST_TYPE","external")')
The following example specifies that the policy set apply only to requests from non-external clients.
wls:/wls-domain/serverConfig> setPolicySetConstraint('!HTTPHeader("VIRTUAL_HOST_TYPE","external")')
Note:
This command has been deprecated. It is recommended that you use the setWSMPolicySetDescription command, as described in "setWSMPolicySetDescription". The following examples show how to migrate to use the setWSMPolicySetDescription command.
11g Release:
wls:/jrfServer_domain/serverConfig> setPolicySetDescription ('Global policy set for web service endpoint.')
12c Release:
wls:/jrfServer_domain/serverConfig> setWSMPolicySetDescription ('Global policy set for web service endpoint.')
Command Category: Policy Set Management
Use with WLST: Online
Specifies a description for a policy set selected within a session.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
Note:
This command has been deprecated. It is recommended that you use the setWSMPolicyOverride command, as described in "setWSMPolicyOverride". The following examples show how to migrate to use the setWSMPolicyOverride command.
11g Release:
wls:/jrfServer_domain/serverConfig> setPolicySetPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')
12c Release:
wls:/jrfServer_domain/serverConfig> setWSMPolicyOverride ('oracle/wss_username_token_service_policy', 'reference.priority', '10')
Command Category: Policy Set Management
Use with WLST: Online
Adds a configuration override, described by a name, value pair, to an attached policy reference in the current policy set. The value argument is optional. If the value argument is omitted, the property specified by the name argument is removed from the policy reference in the policy set. If the property specified by the name argument already exists and a value argument is provided, the current value is overwritten by the new value specified with the value argument.
Issuing this command outside of a session containing a policy set that is being created or modified results in an error.
setPolicySetPolicyOverride(uri,name,[value=None])
| Argument | Definition |
|---|---|
|
|
String representing the OWSM policy URI, for example, |
|
|
String representing the name of the override property. For example: |
|
|
Optional. String representing the value of the property. If this argument is not specified, the property specified by the |
The following example specifies a configuration override for the reference.priority property for the oracle/wss10_saml_token_service_policy to a value of 1.
wls:/wls-domain/serverConfig> setPolicySetPolicyOverride('oracle/wss10_saml_token_service_policy', 'reference.priority','1')
The following example removes the property reference.priority from the oracle/wss10_saml_token_service_policy in the policy set.
wls:/wls-domain/serverConfig> setPolicySetPolicyOverride('oracle/wss10_saml_token_service_policy', 'reference.priority')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, specifies a constraint value for a policy set selected within a session. Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
For more information, see "Specifying Run-time Constraints in Policy Sets" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
setWSMPolicySetConstraint(constraint)
| Argument | Definition |
|---|---|
|
|
Expression that specifies the run-time context to which the policy set applies. If not specified, the policy set applies to all run-time contexts. |
The following example specifies that the policy set applies only to requests from external clients.
wls:/wls-domain/serverConfig> setWSMPolicySetConstraint('HTTPHeader("VIRTUAL_HOST_TYPE","external")')
The following example specifies that the policy set applies only to requests from non-external clients.
wls:/wls-domain/serverConfig> setWSMPolicySetConstraint('!HTTPHeader("VIRTUAL_HOST_TYPE","external")')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, specifies a description for a policy set. Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
setWSMPolicySetDescription(description)
| Argument | Definition |
|---|---|
|
|
Describes a policy set. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, adds a configuration override, described by a name-value pair, to the currently selected policy set. The override is unscoped to any specific policy reference. The value argument is optional. If the value argument is omitted, a null is assumed for value, and the property specified by the name argument is removed from the policy set. If the property specified by the name argument already exists and a value argument is provided, the current value is overwritten by the new value.
You must start a session and select the policy set (using the selectWSMPolicySet command), before initiating the command. Issuing this command outside of a session containing a policy subject that is being created or modified results in an error.
setWSMPolicySetOverride(name,[value=None])
| Argument | Description |
|---|---|
|
|
String representing the name of the override property. For example: |
|
|
Optional. String representing the value of the property. If this argument is not specified, a null is assumed and the property specified by the |
The following example specifies a configuration override for the on.behalf.of property for the policy set selected in the session to a value of true.
wls:/wls-domain/serverConfig> setWSMPolicySetOverride('on.behalf.of','true')
The following example removes the property on.behalf.of from the policy set.
wls:/wls-domain/serverConfig> setWSMPolicySetOverride('on.behalf.of')
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, sets an expression that attaches a policy set to the specified resource scope. The expression must define a valid resource scope in a supported format.
Issuing this command outside of a session containing a policy set that is being created or modified will result in an error.
setWSMPolicySetScope(expression)
| Argument | Definition |
|---|---|
|
|
Expression that attaches the policy set to the specified resource scope. For details about specifying the resource scope expression, see "Defining the Resource Scope" in Securing Web Services and Managing Policies with Oracle Web Services Manager. |
The following example attaches a policy set to the specified base_domain resource.
wls:/wls-domain/serverConfig>setWSMPolicySetScope('Domain("base_domain")')
This example attaches a policy set to the specified base_domain and managed_server resources.
wls:/wls-domain/serverConfig>setWSMPolicySetScope('Domain("base_domain") and Server("managed_server")')
Note:
This command has been deprecated. It is recommended that you use the validateWSMPolicySet command, as described in "validateWSMPolicySet". The following examples show how to migrate to use the validateWSMPolicySet command.
11g Release:
wls:/jrfServer_domain/serverConfig> validatePolicySet ('myPolicySet')
12c Release:
wls:/jrfServer_domain/serverConfig> validateWSMPolicySet ('myPolicySet')
Command Category: Policy Set Management
Use with WLST: Online
Validates an existing policy set. If a policy set name is provided, the command will validate the specified policy set. If no policy set name is specified, the command will validate the policy set in the current session.
An error message displays if the policy set does not exist, or a name is not provided and the session is not active, or if the OWSM repository does not contain a suitable policy set.
validatePolicySet([name=None])
| Argument | Definition |
|---|---|
|
|
Optional. Name of the policy set to validate. If a name is not provided then the command will validate the policy set being created or modified in the current session. |
Note:
This command applies to Oracle Infrastructure and RESTful Web services. It does not apply to Java EE Web services in this release.
Command Category: Policy Set Management
Use with WLST: Online
Within a session, validates an existing policy set. If a policy set name is provided, the specified policy set is validated. If no policy set name is specified, the policy set in the current session is validated.
If the policy set does not exist, if a name is not provided and the session is not active, or if the repository does not contain a suitable policy set, an error message is displayed.
validateWSMPolicySet([name=None])
| Argument | Definition |
|---|---|
|
|
Optional. Name of the policy set to validate. If a name is not provided then the command will validate the policy set being created or modified in the current session. |
Use the commands listed in Table 3-10 to manage the Oracle Infrastructure Web Services documents stored in the OWSM repository. For additional information about upgrading or migrating documents in an OWSM repository, see "Upgrading the Repository to 12c" in the Securing Web Services and Managing Policies with Oracle Web Services Manager.
Note:
The repository management commands listed in Table 3-11 have been deprecated in this release.
To manage the OWSM repository in release 12c, it is recommended that you use the new WLST commands listed in Table 3-10. For a complete list of deprecated commands, see "Deprecated Commands for Oracle Infrastructure Web Services" in Release Notes.
Additional MDS WLST commands are described in Chapter 4, "Metadata Services (MDS) Custom WLST Commands."
Table 3-10 Oracle Infrastructure Web Services - WLST Commands for Repository Management
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Export a set of applications metadata from the repository into a supported ZIP archive. Note: This command is supported for Oracle Infrastructure and RESTful Web services only. This command is not supported for ADF DC Web service clients and Java EE Web services. |
Online |
|
|
Export a set of documents from the repository into a supported ZIP archive. |
Online |
|
|
Import a set of documents from a supported ZIP archive into the repository. |
Online |
|
|
Migrate the custom roles and policies from the |
Online |
|
|
Migrates direct (local) policy attachments that are identical to the external global policy attachments that would otherwise be attached to each policy subject in the current domain. |
Online |
|
|
Delete the existing policies stored in the repository and refresh it with the latest set of predefined policies that are provided in the new installation of the Oracle Fusion Middleware software. |
Online |
|
|
Upgrade the OWSM predefined policies stored in the repository with any new predefined policies that are provided in the latest installation of the Oracle Fusion Middleware software. |
Online |
Table 3-11 list the WLST commands for managing the OWSM repository that have been deprecated in this release.
Table 3-11 Deprecated WLST Commands for Repository Management
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Export a set of documents from the repository into a supported ZIP archive. If the specified archive already exists, you can choose whether to overwrite the archive or merge the documents into the existing archive. |
Online |
|
|
Import a set of documents from a supported ZIP archive into the repository. You can provide the location of a file that describes how to map a physical information from the source environment to the target environment. |
Online |
|
|
Delete the existing policies stored in the repository and refresh it with the latest set of predefined policies that are provided in the new installation of the Oracle Fusion Middleware software. |
Online |
|
|
Upgrade the OWSM predefined policies stored in the repository with any new predefined policies that are provided in the latest installation of the Oracle Fusion Middleware software. |
Online |
Note:
This command has been deprecated. It is recommended that you use the exportWSMRepository command, as described in "exportWSMRepository". The following examples show how to migrate to use the exportWSMRepository command.
11g Release:
wls:/jrfServer_domain/serverConfig> exportRepository ("/tmp/repo.zip")
12c Release:
wls:/jrfServer_domain/serverConfig> exportWSMRepository ("/tmp/repo.zip")
Command Category: OWSM Repository Management
Use with WLST: Online
Exports a set of documents from the OWSM repository into a supported ZIP archive. If the specified archive already exists, the following options are presented:
The specified archive already exists. Update existing archive? Enter "yes" to merge documents into existing archive, "no" to overwrite, or "cancel" to cancel the operation.
You can also specify a list of the documents to be exported, or use a search expression to find specific documents in the repository.
Read only documents, such as predefined policies and assertion templates, will not be included in the export.
exportRepository(archive,[documents=None],[includeShared='false'])
| Argument | Definition |
|---|---|
|
|
Name of the archive file. If the specified archive already exists, you can choose whether to overwrite the archive or merge the documents into the existing archive. During override, the original archive is backed up and a message describes the location of the backup archive. |
|
|
Optional. The documents to be exported to the archive. If no documents are specified, then all assertion templates, intents, policies, and policy sets will be exported. You can specify a list of the documents to be exported, or use a search expression to find specific documents in the repository. |
|
|
Optional. Specifies whether the policy references should be expanded during export. |
The following examples describe repository export sessions. The first example exports all OWSM documents to the policies.zip file.
wls:/wls-domain/serverConfig>exportRepository("/tmp/policies.zip")
This example exports only the MyPolicySet1, MyPolicySet2, and MyPolicySet3 policy sets to the policies.jar file, and also expands all the policy references output during the export process.
wls:/wls-domain/serverConfig>exportRepository("/tmp/policies.jar", ["/policysets/MyPolicySet1","/policysets/MyPolicySet2","/policysets/MyPolicySet3"], true)
This example exports policy sets using wildcards to the some_global_with_noreference_2 file.
wls:/wls-domain/serverConfig>exportRepository('./export/some_global_with_noreference_2', ['policysets:global/web_%','policysets:global/web_ref%', 'policysets:global/web_call%'], false)
Note:
This command is supported for Oracle Infrastructure and RESTful Web services only. This command is not supported for ADF DC Web service clients and Java EE Web services.
Command Category: OWSM Repository Management
Use with WLST: Online
Exports a set of application metadata from the repository into a supported ZIP archive. If the specified archive already exists, you are presented with a set of options: merge the documents into the existing archive, overwrite the archive, or cancel the operation. By default, all metadata for applications in the current domain is exported to the archive, or you can use a search expression to export specific metadata for applications in the repository.
Note:
Read only documents, such as predefined policies and assertion templates, will not be included in the export.
exportWSMAppMetadata(archive,[applications=None],[includeShared='false'])
| Argument | Description |
|---|---|
|
|
Name of the archive file. If the specified archive already exists, you can choose whether to overwrite the archive or merge the documents into the existing archive. During override, the original archive is backed up and a message describes the location of the backup archive. |
|
|
Optional. The metadata of applications to be exported to the archive. If no application names are specified, then all metadata for applications in the current domain will be exported. You can specify a list of search expressions to find specific application metadata in the repository, using this syntax: /{ |
|
|
Optional. Specifies whether the shared documents (those that are specified as policy references within wsm-assembly documents) should be included during export. Because read-only documents can not be exported, only custom or cloned shared policies will be included in the export. |
The first example exports the application metadata in the repository into the applications.zip file and saves it in the tmp directory.
The second example exports the metadata of the applications whose names begin with SalesApp and TradeApp into the applications.zip file and saves it in the tmp directory.
The third example exports the metadata of the applications whose names begin with SalesApp and TradeApp into the applications.zip file and saves it in the tmp directory. Additionally, shared resources are included in this export.
wls:/wls-domain/serverConfig> exportWSMAppMetadata("/tmp/applications.zip") wls:/wls-domain/serverConfig> exportWSMAppMetadata("/tmp/applications.zip",["/WLS/base_domain/SalesApp%","WLS/base_domain/TradeApp%"]) wls:/wls-domain/serverConfig> exportWSMAppMetadata("/tmp/applications.zip",["/WLS/base_domain/SalesApp%","WLS/base_domain/TradeApp%"], true)
Command Category: OWSM Repository Management
Use with WLST: Online
Exports a set of documents from the OWSM repository into a supported ZIP archive. If the specified archive already exists, the following options are presented:
The specified archive already exists. Update existing archive? Enter "yes" to merge documents into existing archive, "no" to overwrite, or "cancel" to cancel the operation.
You can also specify a list of the documents to be exported, or use a search expression to find specific documents in the repository.
Note:
Read only documents, such as predefined policies and assertion templates, will not be included in the export.
exportWSMRepository(archive,[documents=None],[includeShared='false'])
| Argument | Definition |
|---|---|
|
|
Name of the archive file. If the specified archive already exists, you can choose whether to overwrite the archive or merge the documents into the existing archive. During override, the original archive is backed up and a message describes the location of the backup archive. |
|
|
Optional. The documents to be exported to the archive. If no documents are specified, then only shared documents that include policies and policy sets will be exported. If this argument is specified as an empty string |
|
|
Optional. Specifies whether the shared documents (those that are specified as policy references within policy sets and wsm-assembly documents) should be included during export. Because read-only documents can not be exported, only custom or cloned shared policies will be included in the export. |
The following examples describe repository export sessions. The first example exports all OWSM documents to the policies.zip archive.
wls:/wls-domain/serverConfig>exportWSMRepository("/tmp/policies.zip")
This example exports only the MyPolicySet1, MyPolicySet2, and MyPolicySet3 policy sets to the policies.jar archive, and also expands all the policy references output during the export process.
wls:/wls-domain/serverConfig>exportWSMRepository("/tmp/policies.jar", ["/policysets/MyPolicySet1","/policysets/MyPolicySet2","/policysets/MyPolicySet3"], true)
This example exports policy sets using wildcards to the some_global_with_noreference_2 archive.
wls:/wls-domain/serverConfig>exportWSMRepository('./export/some_global_with_noreference_2', ['policysets:global/web_%','policysets:global/web_ref%', 'policysets:global/web_call%'], false)
Note:
This command has been deprecated. It is recommended that you use the importWSMArchive command, as described in "importWSMArchive". The following examples show how to migrate to use the importWSMArchive command.
11g Release (for repository documents):
wls:/jrfServer_domain/serverConfig> importRepository ("/tmp/repo.zip")
12c Release (for repository documents):
wls:/jrfServer_domain/serverConfig> importWSMArchive ("/tmp/repo.zip")
Command Category: OWSM Repository Management
Use with WLST: Online
Imports a set of documents from a supported ZIP archive into the OWSM repository. You can use the map argument to provide the location of a file that describes how to map physical information from the source environment to the target environment. For example, you can use the map file to ensure that the attachment expression in a policy set document is updated to match the target environment, such as Domain("foo")=Domain("bar").
Read only documents, such as predefined policies and assertion templates, will not be included in the import.
importRepository(archive,[map=None],[generateMapFile='false'])
| Argument | Definition |
|---|---|
|
|
Path to the archive file that contains the list of documents to be imported. If a document being imported is a duplicate of the current version that already exists in the repository, then it will not be imported and a new version of the document is not created |
|
|
Optional. Location of a sample map file that describes how to map physical information from the source environment to the target environment. You can generate a new map file by setting the If you specify a map file without setting the |
|
|
Optional. Specify whether to create a sample map file at the location specified by the map argument. No documents are imported when this argument is set to After the map file is created you can edit it using any text editor. The map file contains the document names given in the archive file and their corresponding Note: When importing documents into the repository, OWSM validates the |
The following examples describe repository import sessions.
The first example imports the contents of the policies.zip file into the repository.
wls:/wls-domain/serverConfig>importRepository("/tmp/policies.zip")
This example uses the generateMapFile argument to generate a map file.
wls:/wls-domain/serverConfig>importRepository("./export/some_global_with_noreference_2', map="./export/some_global_with_noreference_2_map', generateMapFile=true)
Here is an example of a generated map file:
This is an auto generated override file containing the document names given in
the archive file and their corresponding attachTo values. The attachTo value can
be updated according to the new environment details. If there is no update
required for any document name,that entry may be either deleted or commented
using the character ("#")
[Resource Scope Mappings
]
web_callback_add_1=Application("*")
web_client_add_1=Module("*")
web_reference_add_1=Domain("*")
web_service_add_1=Domain("*domain*") and Server("*soa*") and Application("*ADF*")
ws_service_no_1=Server("*Admin*")
This example illustrates how to import documents using a generated map file: /some_global_with_noreference_2_map.
wls:/wls-domain/serverConfig>importRepository('../export/export_all', 'export_all_map')
Command Category: OWSM Repository Management
Use with WLST: Online
Imports a set of documents from a supported ZIP archive into the OWSM repository. You can use the map argument to provide the location of a file that describes how to map physical information from the source environment to the target environment. For example, you can use the map file to ensure that the attachment expression in a policy set document is updated to match the target environment, such as Domain("foo")=Domain("bar").
Read only documents, such as predefined policies and assertion templates, will not be included in the import.
importWSMArchive(archive,[map=None],[generateMapFile='false'])
| Argument | Definition |
|---|---|
|
|
Name of the archive file. |
|
|
Optional. Location of a sample map file that describes how to map physical information from the source environment to the target environment. You can generate a new map file by setting the If you specify a map file without setting the |
|
|
Optional. Specify whether to create a sample map file at the location specified by the map argument. No documents are imported when this argument is set to After the file is created you can edit it using any text editor. The Note: When importing documents into the repository, OWSM validates the |
The following examples describe repository import sessions.
The first example imports the contents of the policies.zip file into the repository.
wls:/wls-domain/serverConfig>importWSMArchive("/tmp/policies.zip")
This example uses the generateMapFile argument to generate a map file.
wls:/wls-domain/serverConfig>importWSMArchive("./export/some_global_with_noreference_2', map="./export/some_global_with_noreference_2_map', generateMapFile=true)
Here is an example of a generated map file:
This is an auto generated override file containing the document names given in
the archive file and their corresponding attachTo values. The attachTo value can
be updated according to the new environment details. If there is no update
required for any document name,that entry may be either deleted or commented
using the character ("#")
[Resource Scope Mappings
]
web_callback_add_1=Application("*")
web_client_add_1=Module("*")
web_reference_add_1=Domain("*")
web_service_add_1=Domain("*domain*") and Server("*soa*") and Application("*ADF*")
ws_service_no_1=Server("*Admin*")
This example illustrates how to import documents using a generated map file: /some_global_with_noreference_2_map.
wls:/wls-domain/serverConfig>importWSMArchive('../export/export_all', 'export_all_map')
Command Category: OWSM Repository Management
Use with WLST: Online
Migrates the custom roles and policies from the Plan.xml file to the wsm-pm.ear policy store. If the Plan.xml file is not used to override default security, then this command will not migrate the wsm-pm.ear policy store.
migrateWSMPMRoles(domain)
| Arguments | Description |
|---|---|
|
domain |
Absolute path to the domain home where the |
Command Category: OWSM Repository Management
Use with WLST: Online
Migrates direct (local) policy attachments that are identical to the external global policy attachments that would otherwise be attached to each policy subject in the current domain. You can specify whether to force the migration, prompt for confirmation before each migration, or simply list the migrations that would occur. A direct policy attachment is identical if its URI is the same as one provided by a global policy attachment, and if it does not have any scoped configuration overrides.
Note:
A direct attachment with an unscoped override will be migrated but an attachment with a scoped override will not. This is because after running the migrateAttachments() command, the enforcement of the policies on all subjects remains the same, even though some policies are globally attached.
Whether forced or prompted, the command lists each direct policy attachment that is migrated. This output will identify the policy subject that was modified, the URI of the identical policy reference, and the name of the global policy attachment document that duplicated the direct attachment.
migrateWSMAttachments([mode='prompt'])
| Argument | Definition |
|---|---|
|
|
The action to be taken for each policy attachment that can be migrated. Valid options are:
If no mode is specified, this argument defaults to |
The following examples describe how to use the repository attachment migration modes.
wls:/wls-domain/serverConfig>migrateWSMAttachments() wls:/wls-domain/serverConfig>migrateWSMAttachments('force') wls:/wls-domain/serverConfig>migrateWSMAttachments('preview') wls:/wls-domain/serverConfig>migrateWSMAttachments('prompt')
Note:
This command has been deprecated. It is recommended that you use the resetWSMRepository command, as described in "resetWSMRepository". The following examples show how to migrate to use the resetWSMRepository command.
11g Release:
wls:/jrfServer_domain/serverConfig> resetWSMPolicyRepository()
12c Release:
wls:/jrfServer_domain/serverConfig> resetWSMRepository()
Command Category: OWSM Repository Management
Use with WLST: Online
Deletes the existing policies stored in the OWSM repository and refresh it with the latest set of predefined policies that are provided in the new installation of the Oracle Fusion Middleware software. You can use the clearStore argument to specify whether to delete all policies, including custom user policies, from the OWSM repository before loading the new predefined policies.
resetWSMPolicyRepository([clearStore='false'])
| Argument | Definition |
|---|---|
|
|
Policies to be deleted. Valid values are:
|
The following example deletes all the policies in the repository, including user policies, and adds the predefined policies provided in the current product installation:
wls:/wls-domain/serverConfig>resetWSMPolicyRepository(true)
Note:
Use integer values 0 (false) or 1 (true) to pass Boolean types on wsadmin and ojbst because the Python version used by these scripting tools may not support Boolean types.
Command Category: OWSM Repository Management
Use with WLST: Online
Deletes the existing policies stored in the repository and refresh it with the latest set of predefined policies that are provided in the latest installation of the Oracle Fusion Middleware software. You can use the clearStore argument to specify whether to delete all policies, including custom user policies, from the repository before loading the new predefined policies.
resetWSMRepository([clearStore='false'])
| Argument | Definition |
|---|---|
|
|
Policies to be deleted. Valid values are:
|
Note:
This command has been deprecated. It is recommended that you use the upgradeWSMRepository command, as described in "upgradeWSMRepository". The following examples show how to migrate to use the upgradeWSMRepository command.
11g Release:
wls:/jrfServer_domain/serverConfig> upgradeWSMPolicyRepository()
12c Release:
wls:/jrfServer_domain/serverConfig> upgradeWSMRepository()
Command Category: OWSM Repository Management
Use with WLST: Online
Upgrades the OWSM predefined policies stored in the OWSM repository with any new predefined policies that are provided in the latest installation of the Oracle Fusion Middleware software. If the repository is empty, all of the predefined policies included in the installation are loaded into the repository.
This command does not remove any existing predefined and user-defined custom policies in the repository. If a predefined policy has been modified or discontinued in a subsequent release, one of the following occurs:
For policies that have been discontinued, a message is displayed listing the discontinued policies. In this case, Oracle recommends that you no longer reference the policies and remove them using Oracle Enterprise Manager.
For policies that have changed in the subsequent release, a message is displayed listing the changed policies. Oracle recommends that you import the latest version of the policies using Oracle Enterprise Manager.
Command Category: OWSM Repository Management
Use with WLST: Online
Upgrades the OWSM predefined policies stored in the repository with any new predefined policies that are provided in the latest installation of the Oracle Fusion Middleware software. If the repository is empty, all of the predefined policies included in the installation are loaded into the repository.
This command does not remove any existing predefined and user-defined custom policies in the repository. If a predefined policy has been modified or discontinued in a subsequent release, one of the following occurs:
For policies that have been discontinued, a message is displayed listing the discontinued policies. In this case, Oracle recommends that you no longer reference the policies and remove them using Oracle Enterprise Manager.
For policies that have changed in the subsequent release, a message is displayed listing the changed policies. Oracle recommends that you import the latest version of the policies using Oracle Enterprise Manager.
Use the WLST commands listed in Table 3-12 to view and define trusted issuers, trusted distinguished name (DN) lists, and token attribute rule filters for SAML trusted issuers.
When using WLST to create, modify, and delete token issuer trust documents, you must execute the commands in the context of a session. Each session applies to a single trust document only.
For additional information about using these commands, see "Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
Note:
The commands in this section apply to Oracle Infrastructure Web Services only.
To view the help for the WLST commands described in this section, connect to a running instance of the server and enter help('wsmManage').
Table 3-12 Web Services Token Issuer Trust Commands
| Use this command... | To... | Use with WLST... |
|---|---|---|
|
Create a new token issuer trust document using the name provided. |
Online |
|
|
Delete the entry for the issuer, including the DN list in it. |
Online |
|
|
Delete a token attribute rule associated with a trusted DN. |
Online |
|
|
Delete the token issuer trust document, specified by the name argument, from the repository. |
Online |
|
|
Display the names of the DN lists associated with a specified issuer. |
Online |
|
|
List the token issuer trust documents in the repository. |
Online |
|
|
Select the token issuer trust document, identified by the name argument, to be modified in the session. |
Online |
|
|
Specify a trusted SAML issuer with a DN list. |
Online |
|
|
Add, delete, or update token attribute rules for a given token signing certificate DN. |
Online |
|
|
Sets or resets the display name of the Token Issuer Trust document currently selected in the session. |
Online |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Within a session, creates a new token issuer trust document using the name provided.
You must start a session (beginWSMSession) before creating or modifying any token issuer trust documents. If there is no current session or there is already an existing modification process, an error is displayed.
For more information on using this command, see "Configuring SAML Trusted Issuers, DN Lists, and Token Attribute Rules Using WLST" in Securing Web Services and Managing Policies with Oracle Web Services Manager.
createWSMTokenIssuerTrustDocument(name, displayName)
| Arguments | Definition |
|---|---|
|
|
Name of the document to be created. An error is thrown if a name is not provided. |
|
|
Optional. Display name for the document. |
In the following example, the trust document named tokenissuertrustWLSbase_domain is created, with a display name of wls_domain Trust Document. In the second example, no display name is provided.
wls:/wls-domain/serverConfig> createWSMTokenIssuerTrustDocument("tokenissuertrustWLSbase_domain","wls_domain Trust Document") wls:/wls-domain/serverConfig> createWSMTokenIssuerTrustDocument("tokenissuertrustWLSbase_domain")
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Within a session, deletes the list of all the trusted key identifiers matching the type (such as dns.hok or dns.sv) for the issuer specified. This issuer must exist in the token issuer trust document selected in the session for modification. If no trusted key identifiers exist, then the issuer itself is deleted.
To delete a specified list of trusted key identifiers for an issuer, use selectWSMTokenIssuerTrustDocument.
You must start a session (beginWSMSession) and select a token issuer trust document for modification before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
You cannot modify the default token issuer trust document.
deleteWSMTokenIssuerTrust(type, issuer)
| Arguments | Definition |
|---|---|
|
|
Type of issuer to be deleted, such as |
|
|
Name of the issuer whose trusted DN list will be deleted. |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Delete a token attribute rule associated with a trusted DN from the token issuer trust document.
To delete only the list of filter values for an attribute, use the setWSMTokenIssuerTrustAttributeFilter command.
You must start a session (beginWSMSession) and select a token issuer trust document for modification before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
deleteWSMTokenIssuerTrustAttributeRule(dn)
| Arguments | Description |
|---|---|
|
|
The DN of the token signing certificate that identifies the rule to be deleted. |
In the following example, the token attribute rule associated with the 'CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US trusted DN is deleted.
wls:/wls-domain/serverConfig> deleteWSMTokenIssuerTrustAttributeRule('CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US')
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Deletes the token issuer trust document, specified by the name argument, from the repository. The default token issuer trust document cannot be deleted.
deleteWSMTokenIssuerTrustDocument (name)
| Arguments | Definition |
|---|---|
|
|
Name of the token issuer trust document to be deleted. |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Displays the list of all the trusted key identifiers matching the type specified, such as dns.hok or dns.sv, and the issuer name.
You must start a session (beginWSMSession) and select a token issuer trust document for modification before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
displayWSMTokenIssuerTrust(type, issuer=None)
| Arguments | Definition |
|---|---|
|
|
Type of the trusted key identifiers list to be displayed for the issuer. For example, |
|
|
Optional. Name of the trusted issuer for which the trusted key identifiers list is to be displayed. If you do not specify an issuer name, all of the trusted issuers for the given type are listed. |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
When used without any arguments, this command lists all the token issuer trust documents in the repository. If the detail argument is set to true, the display name and the status of the document are also displayed.
You can use the wildcard character (*) in combination with other characters. If no wildcard character is specified in the name argument, the document that matches the name argument exactly is displayed. If the detail argument is set to true, the contents of the document are listed.
This command can be executed inside and outside of a session.
listWSMTokenIssuerTrustDocuments(name=None, detail='false')
| Arguments | Definition |
|---|---|
|
|
Optional. Name of the token issuer trust document. You can use wildcards with this argument. |
|
|
Optional. List the details for the requested document. The default is |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Selects the token issuer trust document, identified by the name argument, to be modified in the session. The name must match the value of the name attribute in the document.
You must start a session (beginWSMSession) before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
You cannot modify the default token issuer trust document.
selectWSMTokenIssuerTrustDocument(name)
| Argument | Definition |
|---|---|
|
|
Name of the document to modified in the session. An error is thrown if a name is not provided. |
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Specify a trusted SAML issuer with a DN list. This command behaves as follows:
If the trusted issuer already exists for the type specified, and you provide a list of DNs or aliases for the trustedKeys argument, the previous list is replaced with the new list. If you enter an empty set ([]) for the trustedDNs argument, then the list of DN values are deleted for the issuer.
If the trusted issuer does not exist for the type specified and you specify a value for the trustedKeys argument, the issuer is created with the associated DN list. If you do not set the trustedKeys argument, a new issuer is created with an empty DN list.
You must start a session (beginWSMSession) and select a token issuer trust document for modification before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
You cannot modify the default token issuer trust document.
setWSMTokenIssuerTrust(type, issuer, [trustedKeys]=None)
| Argument | Definition |
|---|---|
|
|
The type of the tokens issued by the issuer and how the issuer signing the certificates is identified with trusted keys. The following types are supported:
|
|
|
The name of the trusted issuer, for example |
|
|
Optional. List of trusted key identifiers values to set for the specified issuer. |
In the following example, www.yourcompany.com is set as a trusted issuer and a DN list is not specified:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrust('dns.sv', 'www,yourcompany.com', [])
In the following example, the name 'CN=orcladmin, OU=Doc, O=Oracle, C=US' in added to the dns.sv DN list for the www.oracle.com trusted issuer.
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrust('dns.sv', 'www.oracle.com', [['CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US', 'CN=orcladmin, OU=Doc, O=Oracle, C=US'])
In the following example, the list of DN values in the dns.sv DN list is removed from the www.oracle.com trusted issuer:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrust('dns.sv', 'www.oracle.com', [])
In the following example, the alias orakey is specified as the X509 certificate alias for the SAML SV token type for the www.oracle.com trusted issuer:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrust('dn.alias.sv', 'www.oracle.com', ['orakey'])
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Adds, deletes, or updates token attribute rules for a given token signing certificate DN.
Each rule has two parts: a name ID and an attributes part for user attributes that a DN for a signing certificate can assert. The name ID and the attribute can contain a filter with multiple value patterns.
This command behaves as follows:
If the attribute specified by the attr-name argument already exists with a list of filter values and you provide a new list of values for the filters argument, the previous list is replaced with the new list. If you enter an empty set ([]) for the filters argument, then the existing list of filter values is deleted.
If the attribute specified by the attr-name argument does not exist and you specify a list of values for the filters argument, the attribute is created and added to the document with the specified filter values. If you do not provide a value for the filters argument, an error is thrown.
You must start a session (beginWSMSession) and select a token issuer trust document for modification before executing this command. If there is no current session or there is already an existing modification process, an error is displayed.
Note:
You must first use the setWSMTokenIssuerTrust command to configure a list of trusted DN names for an issuer.
setWSMTokenIssuerTrustAttributeFilter(dn, attr-name, filters)
| Argument | Definition |
|---|---|
|
|
The DN of the token signing certificate. |
|
|
The name of the attribute to assert. The value can be as follows:
|
|
|
Optional. List of filters for the attribute. The list has the format [' When |
In the following example, the name ID yourTrustedUser is set as a trusted user for the weblogic trusted DN:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrustAttributeFilter('CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US','name-id', ['yourTrustedUser'])
In the following example, the name IDs jdoe is added to the list of trusted users for the weblogic trusted DN:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrustAttributeFilter('CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US','name-id', ['yourTrustedUser', 'jdoe'])
In the following example, the list of trusted users for the weblogic trusted DN is removed:
wls:/wls-domain/serverConfig> setWSMTokenIssuerTrustAttributeFilter('CN=weblogic, OU=Orakey Test Encryption Purposes Only, O=Oracle, C=US', 'name-id', [])
Note:
This command applies to Oracle Infrastructure Web services only.
Command Category: Token Issuer Trust Configuration
Use with WLST: Online
Sets or resets the display name of the Token Issuer Trust document currently selected in the session.
You must start a session (beginWSMSession) before creating or modifying any token issuer trust documents. If there is no current session or there is already an existing modification process, an error is displayed.
setWSMTokenIssuerTrustDisplayName("displayName")
| Arguments | Definition |
|---|---|
|
|
Name to be set as a display name for the document currently selected for modification in the session. |