Oracle Web Service Manager 11g

Oracle Web Service Manager 11g Message Protection Policy (in WLS) March, 2012

Step-by-Step Instruction Guide Author: Prakash Yamuna Senior Development Manager Oracle Corporation

Message Protection Policy in WLS using Oracle Web Services Manager 11g

Table of Contents Use Case .................................................................................................................................................................................. 4 Description .......................................................................................................................................................................... 4 Objective ............................................................................................................................................................................. 4 Software Requirements .......................................................................................................................................................... 4 Prerequisites ....................................................................................................................................................................... 4 Verified Product Version ..................................................................................................................................................... 4 Potentially Applies to Product Version(s) ........................................................................................................................... 4 Download Main Page .......................................................................................................................................................... 4 Product URLs ....................................................................................................................................................................... 5 Step by Step Instructions ........................................................................................................................................................ 6 Install Location: ................................................................................................................................................................... 6 Create HelloWorld POJO JAX-WS Application..................................................................................................................... 7 Attach Message protection OWSM Security Policy .......................................................................................................... 18 Creating Keystore and Credentials.................................................................................................................................... 22 Configuring Integrated WLS Server to enable enforcing Message protection Policy ....................................................... 23 Copying the Keystore under the right location for Integrated WLS Server ...................................................................... 25 Verifying jps-config.xml in Default Domain ...................................................................................................................... 26 Creating Credentials required for Keystore access ........................................................................................................... 27 Relationship between Keystore, Credential Store, jps-config.xml ................................................................................... 29 Testing with SOAP UI ............................................................................................................................................................ 30 Create SOAP UI Project ..................................................................................................................................................... 30 Create WS-Security Configurations................................................................................................................................... 33 Add Keystore/Certificates ................................................................................................................................................. 34 Add Outgoing WS-Security Configurations ....................................................................................................................... 36 Oracle Corporation | Message Protection Policy | Version 1.0

2


Add Incoming WS-Security Configurations ....................................................................................................................... 42 Appendix ............................................................................................................................................................................... 47 Log Generated the first time any app is run in Integrated WLS Server ............................................................................ 47

Oracle Corporation | Message Protection Policy | Version 1.0

3


Use Case Description This How-To demonstrates how to use OWSM Message Protection policy to secure a JAX-WS Web Service and how to test it with SOAP UI.

Objective The main objective of this How-To:    

Demonstrate the steps required to secure a simple HelloWorld JAX-WS web service in JDeveloper Configure the Integrated WLS Server to enable using OWSM message protection policies to secure HelloWorld JAX-WS Run the HelloWorld JAX-WS web service within the Integrated WLS Server that ships with JDeveloper Configure and Test the HelloWorld JAX-WS with SOAP UI.

Software Requirements Prerequisites # Product 1 Install SOA Suite 11.1.1.6 with JDeveloper 2 SOAP UI Pro 4.0.1

Download URL

Verified Product Version # 1 2 3

Product WebLogic SOA JDeveloper

Release Version 10.3.6 11.1.1.6 11.1.1.6

Potentially Applies to Product Version(s) # Product 1 WebLogic 2 SOA

Release Version 10.3.3, 10.3.4, 10.3.5, 10.3.6 11.1.1.4, 11.1.1.5, 11.1.1.6

Download Main Page http://www.oracle.com/technetwork/middleware/soasuite/downloads/index.html


4


Product URLs Product EM Fusion Middle Control

URL http://admin_host:admin_port/em

Login/Password User: weblogic Password: welcome1

Note: This How-To uses SOAP UI Pro 4.0.1. The steps can vary with other versions of SOAP UI.


5


Step by Step Instructions Install Location: In this How-To JDeveloper has been installed at: D:\Oracle11g\Middleware We will define ORACLE_HOME= D:\Oracle11g\Middleware JDeveloper.exe is at: $ORACLE_HOME\jdeveloper\jdeveloper.exe In this How-To I am running JDeveloper from command line as shown in Figure 1.

Figure 1. Starting JDeveloper with the "-su" option


6


Create HelloWorld POJO JAX-WS Application 1. Start creation of a new application by click on “New Application” in Figure 2.

Figure 2. Click on "New Application"

This is will launch a new application creation wizard.


7


2. Provide the following values as show in Figure 3. “Application Name”:HelloWorldJaxWS “Directory”: D:\JDeveloper\mywork\HelloWorldJaxWS JDeveloper wil create the new application in the above directory. For purposes of this How-To, select “Generic Application” from the Application Template as shown in Figure 3.

Figure 3. Provide Application Name and Folder information

Click on “Next” button, to proceed to the next step.


8


3. Create a Project for the new application by providing Project information like “Project Name”, “Directory” as show in Figure 4. Since we want to create a POJO based Web Service Select “Web Services” from the “Project Technologies” tab. This will automatically also include Java. Figure 4 shows the selected technologies for this project.

Figure 4. Select Project Technologies and provide Project information

Click on “Next” button.


9


4. Complete the New Application creation process by providing package information and leave the defaults for “Java Source Path” and “Output Directory” as shown on Figure 5

Figure 5. Provide Package and other Java Settings

Click on “Finish” button to complete creation of the new application and the project.


10


5. Next we will create a Java Class. To create a Java Class, right click on the “HelloWorld” project under the HelloWorldJaxWS application and select “New” from the Context Menu as shown in Figure 6.

Figure 6. Creating Java Class in a project.

6. This will launch the Dialog show in Figure 7. In the “Current Project Technologies” tab, Select “Java” from the “Categories” on the Left Hand Side and under “Items” panel on the Right Hand side, select “Java Class” as shown in Figure 7. Click on the “OK” button after making the above selections.

Figure 7. Select Java Class from the "New Gallery" Dialog


11


7. This will launch the new “Java Class” Creation Dialog as show in Figure 8. Provide “HelloWorld” as the name of the java class and provide appropriate value for the java package. Retain defaults for the remainder of the fields. Click “OK” to complete the new Java Class creation dialog.

Figure 8. New Java Class creation Dialog

8. JDeveloper will generate code along the lines shown below. package helloworld; public class HelloWorld { public HelloWorld() { super(); } }


12


Add the following lines of code to the HelloWorld class: public String hello(String str) { return "Hello "+ str; }

9. The next step is to basically create a Web Service from the HelloWorld java class created in the previous steps. To create a Web Service, right click on the HelloWorld.java file. Select “Create Web Service…” from the Context menu as shown in Figure 9.

Figure 9. Launch the Web Service Creation Wizard on the HelloWorld POJO class


13


10. From the “Java Web Service creation” wizard, select Java EE 1.5 option. The entire Web Service creation wizard is a multi-step process as show in Figure 10 - Figure 17.

Figure 10. Select Java EE 1.5 from the Java Web Service Creation wizard

Figure 11. Provide Web Service name


14


Figure 12. Retain default SOAP binding

Figure 13. Select the methods that should be exposed as part of the Web Service


15


Figure 14. Skip Additional Classes

Figure 15. Skip specifiying policies


16


Figure 16. Skip providing any Handlers

Figure 17. Finish creation of Web Service


17


Attach Message protection OWSM Security Policy 1. To attach the OWSM message protection policy to the Web Service, “right click” on the HelloWorld.java file in JDeveloper. Select “Web Service Properties…” from the Context menu item Figure 18. This will launch the Dialog box seen in Figure 19.

Figure 18. Define Web Service Properties


18


2. In the Configure Policies Dialog, select “OWSM policies”. Upon selection of the OWSM Policies option, the system will display the list of out of the box policies that are shipped as part of OWSM. Also notice the Default Policy Store location! In this How-To it maps to: “D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain\oracle\store\gmds”

Figure 19. Select OWSM policies option to secure the Web Service


19


3. For the purposes of this How-To, let’s select the :oracle/wss10_message_protection_service_policy as show in Figure 20.

Figure 20. Selection of oracle/wss10_message_protection_service_policy

Click “OK” button to complete the Policy Attachment. Upon completion of the PolicyAttachment, the @SecurityPolicy annotation will be added to the HelloWorld POJO class as show in Figure 21.


20


Figure 21. Code view with SecurityPolicy annotation


21


Creating Keystore and Credentials 4. In order to use the oracle/wss10_message_protection_service_policy, we need Keystore and Credentials. First we will create keystore using the keytool command as shown in Figure 22. The command to create the keystore using keytool. (Note: Keytool is shipped with JDK).

$> keytool -genkey -keyalg RSA -alias orakey -keystore default-keystore.jks -storepass welcome1 -validity 3600

Figure 22. Keystore creation command and steps.

You can validate the contents of the keystore by using the following keytool command: $>keytool -list -keystore default-keystore.jks -storepass welcome1

Figure 23. Check contents of Keystore using keytool


22


Configuring Integrated WLS Server to enable enforcing Message protection Policy In order to be able to deploy the HelloWorld POJO Web Service to Integrated WLS Server and test the enforcement of the OWSM oracle/wss10_message_protection_service_policy – we need to configure the WLS Domain in which Integrated WLS Server runs; however initially upon the Install the domain is not created completely. You can ensure the domain is created completely by trying to the “HelloWorld” Web Service. You do this by “right clicking” on HelloWorld.java and selecting “Run” from the Context Menu as show in Figure 24

Figure 24. Running HelloWorld Web Service in Integrated WLS Server first time.


23


The appendix shows the log that is output by the system in JDeveloper. The key aspect that is of interest here are the following messages: [Waiting for the domain to finish building...] [09:47:56 PM] Creating Integrated Weblogic domain... [09:50:03 PM] Extending Integrated Weblogic domain... [09:50:51 PM] Integrated Weblogic domain processing completed successfully. *** Using port 7101 *** D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain\bin\startWebLogic.cmd [waiting for the server to complete its initialization...] As mentioned earlier the key thing to note is: On running this the first time – the domain for running the Integrated WLS is extended and the necessary artifacts are created. By default this domain is called “DefaultDomain”. In this scenario the “DefaultDomain” is located at: D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain


24


Copying the Keystore under the right location for Integrated WLS Server 5. Copy the default-keystore.jks created earlier to “D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain\config\fmwconfig” as shown in Figure 25.

Figure 25. Copying default-keystore.jks under "DefaultDomain"


25


Verifying jps-config.xml in Default Domain 6. The jps-config.xml will be found under: D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain\config\fmwconfig: The most important entry in jps-config.xml that is of interest is the following keystore service entry: Default JPS Keystore Service The next step is to configure the credentials in the DefaultDomain.


26


Creating Credentials required for Keystore access Ensure the Integrated WLS Server is running. 7. Start WLST from D:Oracle11g\Middleware\ oracle_common\common\bin\wlst.cmd as shown in Figure 26.

Figure 26. Starting WLST for Integrated WLS Server.


27


8. Connect to the Integrated WLS Server running DefaultDomain as show in Figure 27.

Figure 27. Connect to Integrated WLS Server

Once connected, add the following credentials to the credential store: $> createCred(map="oracle.wsm.security", key="keystore-csf-key", user="owsm", password="welcome1", desc="Keystore key") $>createCred(map="oracle.wsm.security", key="enc-csf-key", user="orakey", password="welcome1", desc="Encryption key") $>createCred(map="oracle.wsm.security", key="sign-csf-key", user="orakey", password="welcome1", desc="Signing key")


28


Relationship between Keystore, Credential Store, jps-config.xml 9. Many people find the relationship between keystore, keys, credential store, credentials and jps-config.xml confusing. Figure 28 shows the relationship between all these artifacts.

Figure 28. Relationship b/w Keystore, Credential Store, Credentials and jps-config.xml


29


Testing with SOAP UI 1. Before testing the Web Service with SOAP UI, Run the HelloWorld from within JDeveloper as shown in Figure 24.

Create SOAP UI Project 2. To test the HelloWorld Web Service secured with the OWSM “oracle/wss10_message_protection_service_policy”, start SOAP UI and create a new Project as shown in Figure 29.

Figure 29. Create new project in SOAP UI


30


3. Provide "Project Name” and “WSDL” information for the HelloWorld WS as show in Figure 30.

Figure 30. Provide WSDL information for the Web Service that needs to be tested


31


4. Double click on the helloworld-msg-prot-test SOAP UI project to open various configurations one can specify for the project as show in Figure 31. Click on the WS-Security Configurations tab.

Figure 31. Specify the WS-Security Configurations


32


Create WS-Security Configurations 5. There are 3 sub-tabs under the “WS-Security Configurations” tab in SOAP UI. These are the “Outgoing WS-Security Configurations” tab, “Incoming WS-Security Configurations” tab and the “Keystore/Certificates” tab. We will first fill out the Keystores/Certificates tab. Click on the Keystore/Certificates tab as shown in Figure 32.

Figure 32. Specify the Keystore/Certificates to be used by SOAP UI


33


Add Keystore/Certificates 6. Click on the “+” button to add a keystore as shown in Figure 33. This will launch a dialog to select the Key Material as show in Figure 34. You will be prompted for the password to the default-keystore.jks. Enter “welcome1” as show in Figure 35.

Figure 33. Adding a Keystore

Figure 34. Select a JKS keystore from the file system.


34


Figure 35. Specify Password for the default-keystore.jks

7. Figure 36 shows the result of adding the default-keystore.jks to SOAP UI.

Figure 36. Result of adding default-keystore.jks

NOTE: For purposes of simplicity – I have selected the same default-keystore.jks file that was used by the HelloWorld Web Service in practice, the client and service DO NOT share the same keystore, instead you should use separate keystores and exchange the public certificates of the client and the service.


35


Add Outgoing WS-Security Configurations 8. The next step is to add the “Outgoing WS-Secure Configurations” to the project. You can do this by click on the Outgoing S-Security Configurations tab and clicking on the “+” icon as shown in Figure 37

Figure 37. Initiate addition of Outgoing WS-Security Configuration


36


9. Enter the “Name” of the configuration as “wss10”. This will create a panel on the lower half of the screen to add relevant WS-Security Configuration for “wss10”. Click on the “+” icon highlighted with a red circle in Figure 38. We need to add 3 entries in the following order: a. Timestamp b. Signature c. Encryption Upon clicking the “+” icon an “Add WSS Entry” popup dialog will be presented which contains a single drop down list. Select “Timestamp” from the dialog as shown in Figure 39.

Figure 38. Adding WSS Configuration for "wss10"

Figure 39. Add Timestamp

10. Configure the “Timestamp” WSS Entry. The two fields are shown in Figure 40: Oracle Corporation | Message Protection Policy | Version 1.0

37


a. Time to Live: 5000 b. Leave the unit for “Time to Live” in milliseconds.

Figure 40. Specify Time to Live as part of Timestamp configuration

11. Add the “Signature” WSS Entry by clicking on the “+” icon again as shown in Figure 38 and selecting “Signature” from the “Add WSS Entry” drop down as shown in Figure 41.

Figure 41. Select Signature WSS Entry to Add to wss10 configuration


38


12. The “Signature” configuration is more involved and requires a lot more fields to be filled in as shown in Figure 42. Here is a summary of the fields and values that need to be provided: a. Keystore: Select “default-keystore.jks” from the drop down. (Note: Only keystores added in the Keystore/Certificates tab will be displayed in this drop down). b. Alias: “orakey”. This particular keystore in the How-To has only a single alias. However a keystore can have multiple keys and aliases. c. Password: “welcome1”. This is the password for the alias. d. Key Identifier Type: Select “Binary Security Token” from the drop down. e. Signature Algorithm: Select “http://www.w3.org/2000/09/xmldsig#rsa-sha1” from the drop down f. Signature Canonicalization: Select “http://www.w3.org/2001/10/xml-exc-c14n#” from the drop down g. Digest Algorithm: Select “http://www.w3.org/2000/09/xmldsig#sha1” from the drop down h. Use Single Certificate: Ensure “Use single certificate for signing” is checked. i. Parts: Name Namespace Encode Body http://schemas.xmlsoap.org/soap/envelope/ Element Timestamp http://docs.oasisElement open.org/wss/2004/01/oasis-200401-wsswssecurity-utility-1.0.xsd

Figure 42. Providing Signature configuration


39


13. Add the “Encryption” WSS Entry, by clicking on the “+” icon again as shown in Figure 38 and selecting “Encryption” from the “Add WSS Entry” drop down as shown in Figure 43.

Figure 43. Adding Encryption WSS entry

14. The “Encryption” configuration is more involved and requires a lot more fields to be filled in as shown in Figure 44. Here is a summary of the fields and values that need to be provided: a. Keystore: Select “default-keystore.jks” from the drop down. (Note: Only keystores added in the Keystore/Certificates tab will be displayed in this drop down). b. Alias: “orakey”. This particular keystore in the How-To has only a single alias. However a keystore can have multiple keys and aliases. c. Password: “welcome1”. This is the password for the alias. d. Key Identifier Type: Select “Binary Security Token” from the drop down. e. Embedded Key Name and Embedded Key Password are not relevant and will be readonly fields. So skip these fields. f. Symmetric Encoding Algorithm: Select “http://www.w3.org/2001/04/xmlenc#aes128-cbc” from the drop down. g. Key Encryption Algorithm: Select “http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p” from the drop down. h. Encryption Canonicalization: Select “http://www.w3.org/2001/10/xml-exc-c14n#” from the drop down. i. Create Encrypted Key: Ensure the checkbox is checked j. Parts: Name Namespace Encode Body http://schemas.xmlsoap.org/soap/envelope/ Content


40


Figure 44. Encryption Configuration


41


Add Incoming WS-Security Configurations 15. Click on the “Incoming WS-Security Configurations” sub tab and click on the “+” icon as show in Figure 45. You will be prompted to enter a name for the incoming configuration, specify “wss10” as the name as shown in Figure 46.

Figure 45. Add Incoming WS-Security Configuration

Figure 46. Provide a name for the Incoming WSS Configuration


42


16. Click on the “wss10” entry and select the following: a. Decrypt Keystore: Select “default-keystore.jks” from the drop down b. Signature Keystore: Select “default-keystore.jks” from the drop down c. Password: “welcome1” The final incoming security configuration is shown in Figure 47

Figure 47. Incoming WSS Configuration


43


17. Now that we have created all the necessary WS-Security Configurations, we are ready to test the HelloWorld Service! To do so click on the “hello” operation on the Left hand browse tree. This will create a request as show in Figure 48. Click on the “Aut” tab on the “Request” panel on the RHS side of the screen. The “Aut” tab is in the bottom and has been highlighted in Figure 48. Select the following values: a. Outgoing WSS: Select “wss10” from the drop down. b. Incoming WSS: Select “wss10” from the drop down.

Figure 48. Select the previosuly created WSS Configuration to be used while testing


44


18. Enter “prakash” for arg0 and click on the green arrow button to send the request. You will be prompted for password – enter “welcome1”. Figure 49 and Figure 50 show the steps and the results of a successful test. If there is a failure – you will see a SOAP response with a fault.

Figure 49. Send request to the HelloWorld WS


45


Figure 50. Results of a successful test


46


Appendix Log Generated the first time any app is run in Integrated WLS Server

[Waiting for the domain to finish building...] [09:47:56 PM] Creating Integrated Weblogic domain... [09:50:03 PM] Extending Integrated Weblogic domain... [09:50:51 PM] Integrated Weblogic domain processing completed successfully. *** Using port 7101 *** D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\DefaultDomain\bin\startWebLogic.cmd [waiting for the server to complete its initialization...] . . JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m XX:MaxPermSize=512m . WLS Start Mode=Development . CLASSPATH=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;D:\ORACLE~1\MIDDLE~ 1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\ORACLE~1\MIDDLE~1\patch_jdev1 111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\ORACLE~1\MIDDLE~1\JDK160~1\lib\tools.jar;D:\ ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\web logic.jar;D:\ORACLE~1\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;D:\ORACLE~1\MIDDLE~1\ WLSERV~1.3\server\lib\webservices.jar;D:\ORACLE~1\MIDDLE~1\modules\ORGAPA~1.1/lib/antall.jar;D:\ORACLE~1\MIDDLE~1\modules\NETSFA~1.0_1/lib/antcontrib.jar;D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~ 1.3\common\derby\lib\derbyclient.jar;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar . PATH=D:\ORACLE~1\MIDDLE~1\patch_wls1035\profiles\default\native;D:\ORACLE~1\MIDDLE~1\patch_jdev1111\pr ofiles\default\native;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\ORACLE~1\MIDDLE~1\WLSERV ~1.3\server\bin;D:\ORACLE~1\MIDDLE~1\modules\ORGAPA~1.1\bin;D:\ORACLE~1\MIDDLE~1\JDK160~1\jre\bin;D:\ ORACLE~1\MIDDLE~1\JDK160~1\bin;D:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\syste m32\WindowsPowerShell\v1.0;D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8 Oracle Corporation | Message Protection Policy | Version 1.0 47 .


*************************************************** * To start WebLogic Server, use a username and * * password assigned to an admin-level user. For * * server administration, use the WebLogic Server * * console at http:\\hostname:port\console

*

*************************************************** starting weblogic with Java version: java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b50) Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode) Starting WLS with line:


48


D:\ORACLE~1\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy Djavax.net.ssl.trustStore=D:\Oracle11g\Middleware\wlserver_10.3\server\lib\DemoTrust.jks Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger Ddomain.home=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1 Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\serv ers\DefaultServer Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1 Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\car ml Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\arisidpr ovider Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\fmwconfig\jpsconfig.xml Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\servers\DefaultServer\t mp\_WL_user -Doracle.deployed.app.ext=\- Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORA CLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false Dwsm.repository.path=D:\ORACLE~1\MIDDLE~1\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\oracle\store\gmds Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;D:\ORA CLE~1\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server


49


Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: ConfigObjectReloaded for ServerConfig. PreviousVersion : -1 : CurrentVersion : 0 Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification event sent for activating changes. Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: AdaptersConfig MBean reloaded Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification sent for AdaptersConfig MBean reloaded Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification sent for Mapping config object reloaded Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: AdaptersConfig MBean reloaded Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification sent for AdaptersConfig MBean reloaded Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: ConfigObjectReloaded for ServerConfig. PreviousVersion : -1 : CurrentVersion : 0 Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info INFO: Notification event sent for activating changes. Mar 16, 2012 9:51:14 PM oracle.ods.virtualization.engine.util.VDELogger info


50


INFO: Notification sent for Mapping config object reloaded IntegratedWebLogicServer startup time: 74437 ms. IntegratedWebLogicServer started. [Running application HelloWorldJaxWS on Server Instance IntegratedWebLogicServer...] [09:52:06 PM] ---- Deployment started. ---[09:52:06 PM] Target platform is (Weblogic 10.3). [09:52:08 PM] Retrieving existing application information [09:52:08 PM] Running dependency analysis... [09:52:08 PM] Deploying 2 profiles... [09:52:09 PM] Wrote Web Application Module to D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\HelloWorldJaxWS\HelloWorldWebApp .war [09:52:10 PM] Wrote Enterprise Application Module to D:\Oracle11g\Middleware\jdeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\HelloWorldJaxWS [09:52:10 PM] Deploying Application... [09:52:13 PM] Application Deployed Successfully. [09:52:13 PM] The following URL context root(s) were defined and can be used as a starting point to test your application: Oracle Corporation | Message Protection Policy | Version 1.0

51


[09:52:13 PM] http://127.0.0.1:7101/HelloWorldJaxWS-HelloWorld-context-root [09:52:13 PM] Elapsed time for deployment: 6 seconds [09:52:13 PM] ---- Deployment finished. ---Run startup time: 6609 ms. [Application HelloWorldJaxWS deployed to Server Instance IntegratedWebLogicServer]

Target URL -- http://127.0.0.1:7101/HelloWorldJaxWS-HelloWorld-context-root/HelloWorldPort


52


Oracle Web Services Manager March 2012 Author: Prakash Yamuna Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com

Copyright © 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. 0109


53

Oracle Web Service Manager 11g

Oracle Web Service Manager 11g

Suggest Documents

Oracle Web Service Manager 11g

Oracle Web Service Manager 11g

ORACLE ENTERPRISE MANAGER 11g MANAGEMENT ...

Oracle Access Manager 11g Integration Guide

Oracle Identity Manager 11g Sizing Guide

Oracle Identity Manager 11g R2: Essentials

Oracle JDeveloper 11g JAX-WS Web Services

ODP.NET 11g - Oracle

Managing Fusion Middleware with Oracle Enterprise Manager 11g

Connecting to Oracle 11g

2.2 ORACLE 11g

Oracle Database 11g

ORACLE IDENTITY MANAGEMENT 11g

ORACLE WEBLOGIC SUITE 11g

Customizing Oracle BIEE 11g

Oracle SOA Suite 11g

2.2 ORACLE 11g

What's New in Oracle Identity Manager 11g R2

pdf-15104\oracle-identity-and-access-manager-11g-for ...

Oracle Enterprise Manager 11g Management Pack for WebLogic ...

pdf-15104\oracle-identity-and-access-manager-11g-for ...

Installation Guide Oracle Enterprise Manager Grid Control 11g on ...

Configuring Oracle Enterprise Manager 11g with Cisco Application ...

Oracle Access Manager 11g R2: Administration Essentials Course ...