Oracle Service Bus 12c - Administration Ed 1 (Activity Guide)

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2016, Oracle and/or its affiliatesฺ

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

Oracle Service Bus 12c: Administration Activity Guide D88517GC10 Edition 1.0 | July 2015 | D91946 Learn more from Oracle University at oracle.com/education/

a

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.


Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

s a h l) ฺ c ฺ l nte uide e Author @ nt G z e u tude Cindy Church q s cva this S f Technical Contributors and Reviewers ( a Wunderlich, dRobert Mary Peek, Takyiu Liu, David J. Mills, Irise Li, Matt Slingsby, Jay Kasi, se u ñ a o Armando Hernandez, William Prewitt t t as nse C z lice Editors e u le Abraham Smita Kommini, Raj Nikita sqKumar, b á a V fer e s p Graphic Designer i l n e a r F Bopaiah -t Seema n o n

Trademark Notice

a

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Publisher Jobi Varghese, Jayanthy Keshavamurthy This book was published using:

Oracle Tutor

Table of Contents Password document for Oracle Service Bus 12c Administration


Practices for Lesson 1: Introduction ..............................................................................................................1-1 Practices for Lesson 1....................................................................................................................................1-2 Practices for Lesson 2: Getting Started with Oracle Service Bus ...............................................................2-1 Practices for Lesson 2....................................................................................................................................2-2 Practices for Lesson 3: Installing Oracle Service Bus 12c ..........................................................................3-1 Practices for Lesson 3: Overview ...................................................................................................................3-2 Practice 3-1: Installing Oracle Service Bus 12c .............................................................................................3-3 Practice 3-2: Installing Service Bus Schemas by Using the Repository Creation Utility .................................3-9 Practice 3-3: Creating a WebLogic Domain for Oracle Service Bus...............................................................3-15 Practice 3-4: Deploying Web Service Applications.........................................................................................3-25 Practice Solutions ..........................................................................................................................................3-27

a s a )h ฺ l c ฺ el ide t n u e G Practices for Lesson 5: Service Bus Management Fundamentals ..............................................................5-1 @ t ez den Practices for Lesson 5: Overview ...................................................................................................................5-2 u q s tu Practice 5-1: Managing Service Bus Sessions ...............................................................................................5-3 a S v Practice 5-2: Customizing a Service Bus Configuration .................................................................................5-9 (fc e this a d us Practice 5-3: Managing Service Bus Using WLST e.........................................................................................5-16 ñ (Optional) Practice 5-4: Propagating a Service Bus Configuration a t to .................................................................5-22 s e a Solution Instructions .......................................................................................................................................5-30 C cens z Practices for Lesson 6: Reporting and Monitoring .......................................................................................6-1 li ue ...................................................................................................................6-2 q e l s Practices for Lesson 6: Overview rabHealth .........................................................................................................6-3 Vá fService Practice 6-1: Monitoring e e sService-Level Agreements ..........................................................................................6-9 ip6-2: Defining l n Practice e a r F n-Analyzing t Practice 6-3: Service Bus Reports .................................................................................................6-18 o n Practices for Lesson 4: Service Bus Administration Tools .........................................................................4-1 Practices for Lesson 4: Overview ...................................................................................................................4-2 Practice 4-1: Testing a SOAP-Based Pipeline ...............................................................................................4-3 Solution Instructions .......................................................................................................................................4-12

Solution Instructions .......................................................................................................................................6-22

Practices for Lesson 7: Service Bus Security ...............................................................................................7-1 Practices for Lesson 7: Overview ...................................................................................................................7-2 Practice 7-1: Configuring the Security Environment .......................................................................................7-4 Practice 7-2: Applying a Security Policy to Proxy Services ............................................................................7-9 Practice 7-3: Testing the Proxy Service Security Implementation ..................................................................7-13 Practice 7-4: Propagating Identity from Service Bus to Secured Web Service ..............................................7-18 Solution Instructions .......................................................................................................................................7-30 Practices for Lesson 8: Service Bus High Availability .................................................................................8-1 Practices for Lesson 8: Overview ...................................................................................................................8-2 Practice 8-1: Creating a Service Bus Cluster .................................................................................................8-3 Practice 8-2: Initializing a Service Bus Cluster ...............................................................................................8-11 Practice 8-3: Load Balancing Service Endpoint .............................................................................................8-15 Practice Solutions ..........................................................................................................................................8-21


Oracle Service Bus 12c: Administration Table of Contents



a


Password document for Oracle Service Bus 12c Administration

Server and Cluster passwords Username: weblogic password: welcome1

Database Sys: dba

s a h l) ฺ c ฺ l nte uide e @ nt G z e Database Schema PROD u tude q s password: oracle cva this S f ( da use e ñ sta se to a Database Schema PROD1 z C en c e i l squ rable password: oracle á V fe e s p i l n e a r F n-t noSchema PROD2 Database password: welcome1

password: oracle

username: jdoe password: welcome1

username: joe password: welcome1

a

For Practice 7-3, step 2d


username: joe password: notwelcome1


a


s a h l) ฺ c ฺ l nte uide e G1: @ t Practices for Lesson z n e u tude q Introduction s va his S c f ( aChapterse1 t d e añ e to u t s Ca cens z ue le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 1: Introduction Chapter 1 - Page 1

a

Practices for Lesson 1


There are no practices for this lesson.



Practices for Lesson 1: Introduction Chapter 1 - Page 2

a


s a h l) ฺ c ฺ l nte uide e G2: @ t Practices for Lesson z n e e u tudwith q Getting Started Oracle s a S v is Service (fc e thBus a ed Chapter us2 ñ a o t t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no


Practices for Lesson 2: Getting Started with Oracle Service Bus Chapter 2 - Page 1

a

Practices for Lesson 2


There are no practices for this lesson.



Practices for Lesson 2: Getting Started with Oracle Service Bus Chapter 2 - Page 2

a


a s a )h ฺ l c ฺ el ide t n u e G @ t Practices for n 3: ez Lesson e u d q Installing s Oracle tu Service Bus a S v 12c (fc e this a ed Chapter us3 ñ a o t t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no


Practices for Lesson 3: Installing Oracle Service Bus 12c Chapter 3 - Page 1

Practices for Lesson 3: Overview


Practices Overview In the practices for this lesson, you: • Install Oracle Service Bus 12c • Run the Oracle Repository Creation Utility to create the Service Bus schemas (to support the reporting feature and Oracle WSM policies) • Create a WebLogic domain for Oracle Service Bus • Deploy back-end web service applications The Oracle WebLogic Server 12.1.3.0 software has already been installed on the classroom machines.




a

Practice 3-1: Installing Oracle Service Bus 12c Overview


In this practice, you install the Oracle Service Bus 12c software.

Assumptions •

•

The Oracle WebLogic Server 12.1.3.0.0 software must be installed in the Oracle Middleware Home directory /u01/app/oracle/fmw_admin/12.1.3.0/wlserver. (This has been installed for you.) Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 is installed.

•

The /home/oracle/stage directory must contain the software for Oracle Service Bus 12c 12.1.3.0. The following environment variables are used in the lab environment and are included in your .bash_profile file: MIDDLEWARE_HOME=/u01/app/oracle/fmw_admin/12.1.3.0 JAVA_HOME=/usr/java/jdk1.7.0_71

a s a )h ฺ l c ฺ el ide t Tasks n u e G t 1. In a terminal window, navigate to the installation directory. z@ e den u q $ cd /home/oracle/stage s tu a S v c javathexecutable is 2. Start the Service Bus installation by invoking(fthe from the JDK directory a on your system. e ed o us ñ a $ /usr/java/jdk1.7.0_71/bin/java st se t –jar fmw_12.1.3.0.0_osb.jar a C some The Oracle installer performs ensystem checks and launches the installation wizard. z c e i l 3. Complete the installation qu busing e the graphical user interface by following the steps below: l s á a. ClickV Next in thera Welcome screen. e f e s b. ip Select the Oracle home directory /u01/app/oracle/fmw_admin/12.1.3.0 using Fel then-drop-down tran menu. no




s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s va his S c f ( t c. Review the Feature Sets included ina the current installation, and then click Next. e d s e añ e to u t s Ca cens z ue le li q s Vá ferab e ip rans l e F n-t no



a


d.

Review the Installation Type, and then click Next.

e.

After the installer does the installation prerequisite checks, click Next.




a


f.

Click Install on the Review the Installation Summary screen.




a


g.

Watch the Installation Summary screen and wait for it to reach 100% complete. All items should have a green check mark in the first column.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen h. Click Next. z e u le li q s Vá ferab e ip rans l e F n-t no



a


i.

Review the Installation Complete screen and click Finish when you are done. The screen shows the next steps in the installation process.




a

Practice 3-2: Installing Service Bus Schemas by Using the Repository Creation Utility


Overview In this practice, you run RCU version 12.1.3.0.0 to create the schemas in the Oracle Database 11g standard edition database instance.

Assumptions • •

Oracle Service Bus 12.1.3.0.0 is installed on the system. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 is installed.

Tasks 1. 2.

Open a terminal window. Navigate to the directory that has the rcu script.

a s a )h ฺ 3. Confirm that JAVA_HOME is set to the correct path. l c ฺ l e efollowing t a. To confirm that the environment variable is set correctly, enter the idcommand: n u e $ java -version @ nt G z e uin the image: de b. Ensure that the Java version is 1.7.0_71, as shown q u s t cva this S f ( da use e ñ ta e to s a c. If you do not see thatC Java version, ns then set JAVA_HOME to e z c /usr/java/jdk1.7.0_71. ue le li q s 4. Confirm thatáMIDDLEWARE_HOME is set to the correct path. ab r V e f e a. ip To confirm s that the environment variable is set correctly, enter the following command: l n e a r F $nls -t $MIDDLEWARE_HOME o b.n Ensure that you see these directories included in the list: osb, oracle_common, $ cd /u01/app/oracle/fmw_admin/12.1.3.0/oracle_common/bin

wlserver.

5.

c. If you do not see those directories, then set MIDDLEWARE_HOME. Run the script. $./rcu

6. 7.

Click Next on the Welcome screen. Accept the default Create Repository option with the System Load and Product Load options selected and click Next.




8.

9.

Enter the following information on the Database Connection Details screen: Host Name: localhost

s a h l) ฺ c ฺ Port: 1521 l nte uide Service Name: orcl e @ nt G z Username: sys e ufile. tude q s Password: See the OracleServiceBus12cPassword cva this S f Role: SYSDBA ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

Click Next.



a


10. After the prerequisite checks have passed, click OK.

a s a )h ฺ l c ฺ 11. Select “Create new prefix” and enter PROD. el ide t n u selections, 12. Expand AS Common Schemas in the Component table and makee the following G @ t and then click Next: ez den u q Metadata Services s tu a S v Audit Services (fc e this a Audit Services Append ed o us ñ a Audit Services Viewer st t e a s Oracle Platform Security C Services n e z c e i l User Messaging qu Service le s b á WebLogic Services a V fer e s Scheduler Oracle Enterprise p i l n e a r F Common -t Infrastructure Services (selected by default) n o n SOA Suite SOA Infrastructure




a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v 13. Verify that the prerequisite checks have passed and then click OK. (fcandeenter histhe password as follows, and t a 14. Select Use same passwords for all schemas ed o us ñ then click Next: a st se t a Password: See the OracleServiceBus12cPassword file. C cen z Confirm Password: See file. e theeOracleServiceBus12cPassword li u q l ás erab V e nsf p i l Fe n-tra no




15. Accept the default custom variables and then click Next.

16. Click Next on the Map Tablespaces screen. a. Click OK in the dialog box to create any tablespaces that do not already exist in the schema.


b.

When the table creation is complete, click OK.



a


17. Review the Summary Creation information and then click Create.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( 18. Verify that each of the component schemas a Success status, and then click a indicates e d s e Close. Do not close the terminal window. You can use it in the next section. ñ to u a t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no



a

Practice 3-3: Creating a WebLogic Domain for Oracle Service Bus Overview


In this practice, you create a WebLogic domain for Oracle Service Bus.

Assumptions •

The Oracle WebLogic Server 12.1.3.0.0 software must be installed in the Oracle Middleware Home directory /u01/app/oracle/fmw_admin/12.1.3.0.

•

The Oracle Service Bus 12c 12.1.3.0.0 is installed into the specific Oracle Home directory /u01/app/oracle/fmw_admin/12.1.3.0.

•

The Oracle Database 11g instance is running with the required Service Bus schemas.

Tasks 1.

Start the Oracle Fusion Middleware Configuration Wizard by entering the following commands in a terminal window:

a s a )h ฺ l c ฺ el ide t n u e G @ t 2. In the Domain Location field, leave the directory the same, except replace base_domain ez den u with osb_domain. q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no $ cd /u01/app/oracle/fmw_admin/12.1.3.0/oracle_common/ common/bin $ ./config.sh

3. 4.

Click Next. Choose the templates. a. Select Create Domain Using Product Templates. b. Select the following available templates: − Oracle Service Bus – 12.1.3.0 [osb] − WebLogic Advanced Web Services for JAX-RPC Extension – 12.1.3.0 [oracle_common] − ODSI XQuery 2004 Components – 12.1.3.0 [oracle_common] − Oracle Enterprise Manager – 12.1.3.0 [em] − Oracle WSM Policy Manager – 12.1.3.0 [oracle_common] − Oracle JRF – 12.1.3.0 [oracle_common] Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



c.

− WebLogic Coherence Cluster Extension – 12.1.3.0 [wlserver] Click Next.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed the us ñ 5. On the Application Location screen, verify domain name and location, and then click a o t t as nse Next. C z lice Domain name: osb_domain e u sq rable Domain location: á V fe /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/domains e s p i l n Application location: e a r F/u01/app/oracle/fmw_admin/12.1.3.0/user_projects/applications/osb_domain -t n o n

6.

Configure the Administrator user name and password using the following settings, and then click Next: Name: See the OracleServiceBus12cPassword file. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.


Password: See the OracleServiceBus12cPassword file (enter twice to confirm).


7.

Select Production for Domain Mode and Oracle HotSpot 1.7.0_71/usr/java/jdk1.7.0_71 for JDK, and then click Next.

a s a )h ฺ l c ฺ 8. Enter the following settings for the Database Configuration Type, and tthen el clickiNext: de n u e Vendor: Oracle @ nt G Version z e Driver: *Oracle’s Driver (Thin) for Service connections; u tude q 9.0.1 and later s cva this S f DBMS/Service: orcl ( da use Host Name: localhost e ñ Port: 1521 sta se to a C cen Schema Owner: PROD_STB z e li u See q e Schema Password: the OracleServiceBus12cPassword file. l s á eOwners rab in this table must match the value that you assigned to schema Note: e TheVSchema f s you ran the RCU utility. Do not leave it at the default with the DEV ip earlier owners when l n e a r Fprefix nbecause -t that is used for a different course. o n the Get RCU Configuration button to retrieve the database schema. 9. Click




10. When the message “Successfully Done” is displayed, click Next.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( 11. Click Next on the Component Datasources a screen. d se e u ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


12. After the datasources have been successfully created, click Next.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v fc this (administration a Note: This creates a default domain with an server and one Service Bus d use e ñ managed server called osb_server1. sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no




13. Select Administration Server and Managed Servers, Clusters and Coherence on the Advanced Configuration screen, and then click Next.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( daServeruscreen, se and then click Next: e ñ 14. Enter the following on the Administration sta se to a Name: AdminServer C cen z Listen Address: localhost e u le li q s Listen Port: á 7001 ab r V e f e Server sUnspecified ip Groups: l n e a r F n-t no



a


s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s 15. Enter the following on the Managed Server screen, cvaandththen is Sclick Next: f ( Name: osb_server1 da use e ñ Listen Address: localhost ta s se to a Listen Port: 7003 C cen z e Server Groups: q OSB-MGD-SVRS-COMBINED u le li s Vá ferab e ip rans l e F n-t no

a

16. Click Next on the Clusters and Coherence Clusters screens. 17. Click Next on the Machines screen. This step is necessary if you are managing several servers, but it is not required for your classroom purposes.




18. Review the details on the Configuration Summary screen, and then click Create.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( 19. When the Configuration Progress reaches e Next. da100%, sclick e u ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


20. Review the information on the Configuration Success screen, and click Finish.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t 21. Start the administration server. a C ways ento start the server. You can simply double-click the z a. There are several differentic e l squ rable á V fe e s p i l n e a r F n-t SA Admin Server icon on the desktop and enter the noStart administrative credentials (See the OracleServiceBus12cPassword file) when prompted. Or you can execute the following commands: 1) Open a new terminal window, and navigate to the /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/domains/osb_ domain/bin directory. 2)

Enter the following command:

$ gnome-terminal -–title “AdminServer” –e ./startWebLogic.sh If prompted, enter the administrative credentials: weblogic/ See the OracleServiceBus12cPassword file. Note: This command starts the server in a separate terminal window with the appropriate title so that you do not confuse it with other terminal windows. You can also start it by using a separate terminal window with just the ./startWebLogic.sh command. Tip: If you prefer, create a boot.properties file for the domain to avoid supplying credentials on subsequent server restarts. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



b.

The server will take a couple of minutes to start up. Make sure that you see the message “Server started in RUNNING mode” to confirm that the Administration server is running.

a s a )h ฺ l c ฺ 22. Start the Service Bus managed server. el ide t n u SA OSB e theGStart a. Similarly, start the Service Bus managed server by double-clicking @ t ez den u q s tu a S v (fc e this a d usand enter the administrative credentials Server icon on the desktop ñe a (see the OracleServiceBus12cPassword st se to file) when prompted. Or you can a Ccommand: execute the following en z c e i l $ gnome-terminal Server” –e squ rable-–title “SBosb_server1” á “./startManagedWebLogic.sh V fe e s enter the administrative credentials: See the p i When prompted, l n e a r F OracleServiceBus12cPassword file. -t n o n Note: You can also start it by using a separate terminal window with just the b.

c.

./startManagedWebLogic.sh osb_server1 command. It will take a couple of minutes to start. Make sure that you see the message “Server started in RUNNING mode” to confirm that the Service Bus managed server is running. Minimize the terminal windows but do not close them. If you close these windows, it will shut down the servers, and you will need to start them again.



Practice 3-4: Deploying Web Service Applications Overview


In this practice, you deploy the back-end web service applications that will be used in later practices.

Tasks 1.

Deploy the back-end web service applications: a. Open a terminal window and navigate to the practices directory: $ cd /home/oracle/labs_SA/Practice_03 b.

Deploy the service applications by using the following command: $ ./deploy_apps.sh

2.

Wait until you see the message Deployment of service applications complete! The Deployment State for each of the six applications should be completed. Verify that all the back-end web service applications are deployed on the WebLogic administration server and are running. a. Double-click the Firefox Web Browser launcher on the desktop and start the Oracle Enterprise Manager Fusion Middleware Control (EM) Console by entering the following URL: http://localhost:7001/em

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s b. Log in using (see the OracleServiceBus12cPassword cva this S file) credentials. f ( If you see an Accessibility Preferences da dialog sebox, click Continue. e u ñ c. In the Target Navigation section, ta expand to WebLogic Domain > osb_domain > s e a AdminServer. C cens z ue le li q s Vá ferab e ip rans l e F n-t no

d.

a

In the Application Deployments section, verify that the following applications are listed under Application Deployments: • • • • •

CreditCardValidationService_WS OrderServices OrderStatusApplication PaymentServices ServiceA_App-Service_A-context-root Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



• • •

ServiceA_App-Service_B-context-root ServiceA_App-Service_C-context-root ShippingServices

a

Note: If you do not see these applications, go back to the terminal window where you ran the deployment script and check back through the messages to see what caused them to fail.





Practice Solutions If you do not have time to complete these practices, perform the following steps. Alternatively, you might face a situation where you made an error while creating the Service Bus domain, or during the course of performing the practices, the Service Bus domain crashes. Follow the instructions in Step 3 as follows to re-create the Service Bus domain to its original state. In this case, the database schemas must already exist and Oracle Service Bus 12c must be installed. Your instructor can give you information for uninstalling a domain, if necessary.

Tasks 1. 2.

Install Oracle Service Bus 12c by following the instructions in Practice 3-1. Create the schemas in the database: a. In a terminal window, navigate to the Solutions directory: $ cd /home/oracle/labs_SA/Practice_03/Solutions b.

Run the script to create the schemas using RCU:

a s a )h ฺ l Verify that the schema was properly created. c ฺ el ide t n u e G @ t ez den u q s tu a 3. Create the Service Bus domain. S v c instructions (fthe his in 3-3 a. Create the Service Bus domain following t a e edservero and b. Start the WebLogic administration usService Bus managed server by ñ a t t following the instructions s the end Practice 3-3. The back-end service ethe ofadministration a nearwhen s C applications will be deployed server starts. n e z c e i l c. Complete Practice qu 3-4, estep 1. l s b á d. VerifyVthat all thera web service applications are deployed and running on the WebLogic e f e administration server by following the instructions in Practice 3-4, step 2. s ip ran l e F n-t no $ ./create_schemas.sh







a


s a h l) ฺ c ฺ l nte uide e G4: @ t Practices for Lesson z n e u Administration de q u Service Bus s t cva this S f Tools ( da use e ñ to 4 sta se Chapter a C cen z e u le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 4: Service Bus Administration Tools Chapter 4 - Page 1

a



Practices Overview In this practice, you test a SOAP-based proxy service. You familiarize yourself with the Test Console and the information it has to offer, including the Request Document, Response Document, and Response Metadata. You also generate an error with one of the proxy services and use the Invocation Trace to see the proxy service error.




a


Practice 4-1: Testing a SOAP-Based Pipeline In this practice, you will use the Fusion Middleware Control Console to: • Test a SOAP-based pipeline • View an error message in the Test Console • Trace the invocation This shows the message flow diagram of the specific services to be tested. ShippingService Diagram (SOAP-Based Service):

s a h Assumptions cl) eฺ • The Oracle Service Bus 12c 12.1.3.0 is installed and is running. telฺ id nare running. u e • The back-end web service applications have been deployed and G t Enterprise z@ n e Note: Throughout the practice guides, the abbreviation FMWC refers to the e u q Stud s Manager Fusion Middleware Control console. a cv this f ( Tasks da use e ñ 1. Deploy the Service Bus project. ta to s e a a. Open a terminal window C andcenavigate ns to the z /home/oracle/labs_SA/Practice_04/deploy_projects directory. e e li u q l s deploy_projects.sh b. Executeáthe script to load the Service Bus project for this b a r V practice (and subsequent practices) into the WebLogic domain. e f e s p i Fel $n./deploy_projects.sh tran noYou should see the following messages at the end: ... Creating a session... Read binary file... Importing the project... Activating the session... Disconnected from weblogic server: AdminServer



a


2. Test the ShippingService pipeline. a. In a browser window, log in to the FMWC Console at http://localhost:7001/em as weblogic/ See the OracleServiceBus12cPassword file.




a


b.

In the Target Navigation section, expand SOA > service-bus (AdminServer) > Practice_04.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s a is S c. Navigate to Service Bus Project > Homec>vOperations. f ( th a e d ñe to us a t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no



a


d.

In the Operations section, select the Shipping Service pipeline.

s a h l) ฺ c ฺ l nte uide e. Click the Test button to launch the Test Console. e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

f.

a

The Test Console launches in a separate browser window. The shipOrder operation takes shipping information and returns a tracking number. In the Payload section, click Browse, navigate to /home/oracle/labs_SA/Practice_04/resources, and open Payload.txt. Note: This proxy service has only one operation; but if it had more, you would start by selecting the operation that you want to test from Available Operations.




s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude g. Click Execute to test the pipeline. q s S va hisDocument h. Observe the Request Document and thecResponse and answer the f ( t following questions: da use e 1) What is the shipper’s first ñ name? ta name? to slast 2) What is the shipper’s e a C type? ns e z 3) What is theeshipping c li u was q e l 4) Whatsresponse returned by the pipeline service? á erab V e nsf p i l Fe n-tra no



a



a

Answers: 1) Harry 2) Potter 3) Fedex 4) Tracking number: Hr14d683c1-3407-407a-a0d0-ee4824066055 (or something similar)




i.

Scroll down to the Invocation Trace section, expand RouteNode1, and then expand added $transformedMsg. What did the proxy do to change the message? What is the name of the shipper?

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu Answers: a S v isFedex model. For example, it a) The proxy transformed the message the (fc into h t a e concatenated the FirstName sand LastName (Potter) to one Name, ed (Harry) u ñ HarryPotter. a o t st b) The shipperC isa fedEx. se z to theliTest cenConsole input page and change the j. Click Back tou return e sq rable node in the Payload to ups. á V fe e s p i l n e a r F n-t no

k.

Execute the test again and inspect Invocation Trace > RouteNode1 > Message Context Changes > added $transformMsg. How does the UPS message type differ from the fedEx one? Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



s a h l) ฺ c ฺ l nte uide e @ nt G z e Answer: The first name and last name are kept separate there u and de is an address q u s t element, Adr, which contains the separate address elements. cva this S f 3. View an error in the Test Console. ( da input sepage. Change the a. Click Back to return to the Test Console e u ñ a Payload toto test. s in tthe e a C cens z ue le li q s Vá ferab e ip rans l e F n-t no

b. c.

d.

a

Execute the test. Check the Response Document. Did the pipeline return a tracking number? If not, what did it return? Answer: The pipeline did not return a tracking number; instead it returned an Internal Server Error. Check the Invocation Trace. What is the fault code and reason? Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



s a h l) ฺ c Answer: The fault code is Server. The reason is that the format was incorrect. ฺ l OrderNumber is meant to be a number and it received a string. nte ide u e e. Close the Test Console. @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a

Solution Instructions


This practice deploys a Service Bus project and then tests the pipeline. If you do not have the time to perform this practice, you can simply deploy the project, using the following steps: 1. Open a terminal window and change the current working directory to the /home/oracle/labs_SA/Practice_04/deploy_projects directory. 2. 3.

Execute the deploy_projects.sh script to load the Service Bus project for this practice into the WebLogic domain. You should see the following messages at the end: ... Creating a session... Read binary file... Importing the project... Activating the session... Disconnected from weblogic server: AdminServer

a s a )h ฺ l c ฺ 4. To confirm that the projects were deployed successfully, perform the following: el ide t n a. In a browser window, log in to the Service Bus Console at http://localhost:7001/em as u e G @ t weblogic/ See the OracleServiceBus12cPassword file. ez den u q b. In the console, click Project Explorer and expand s the Practice_04 tu Notification and a S v Shipping projects. (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

5.

Optionally, you can follow the instructions in Practice 4-1 steps 2 and 3 to test the pipeline.




s a h l) ฺ c ฺ l nte uide e G5: @ t Practices for Lesson z n e u Management de q u Service Bus s t cva this S f Fundamentals ( da use e ñ to 5 sta se Chapter a C cen z e u le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 5: Service Bus Management Fundamentals Chapter 5 - Page 1

a



Practices Overview In the practices for this lesson, you: • Manage Service Bus sessions and resolve concurrency conflicts for a clean activation • Create a customization file to automatically find and replace specific values • Manage Service Bus by using WLST • Propagate a Service Bus configuration from one domain to another (Optional practice)




a

Practice 5-1: Managing Service Bus Sessions


Overview In this practice, you will start to become comfortable with session management in Service Bus. Sessions are used when modifying properties in the administration console, so you will be creating a session, modifying properties of Service Bus resources, and then activating those changes. Before activating your changes, the console notifies you of any conflicts your changes might have caused. You will practice resolving those conflicts for a clean activation. You use two different browser instances to log in to two different Service Bus consoles. You also use different user credentials to log in to simulate a conflicting scenario in modifying Service Bus resources. For simplicity, let’s define: Service Bus Console 1: Mozilla Firefox Web browser instance 1 Service Bus Console 2: Mozilla Firefox Web browser instance 2

Tasks

a s a )h ฺ l c ฺ el ide t n u to e userG("jdoe") b. Execute the create_user.sh script to add a new administrative @ t n the script: osb_domain. Make sure you see the following message ez afterdexecuting e u q s tu a S v (fc e this a ed o us ñ a t orewarnings t Note: You can ignore anyserrors as long as the script indicates that "jdoe" a s C was created successfully. n e z weblicbrowsers. eopen u c. Close all ofq your le as the weblogic user to create a new session. For this s abConsole 2. Log in to V theáServicerBus e 1. fconsole e call this practice, s p i l n Fa.e Open traaFirefox web browser and navigate to the Service Bus Console at n nohttp://localhost:7001/servicebus. 1.

Set up the practice environment. a. In a Terminal window, navigate to /home/oracle/labs_SA/Practice_05/create_user.




b.

Log in with the weblogic/ See OracleServiceBus12cPassword File credentials.

c.

In the top-right corner, click Create to create a new session.

b.

In the Private Window, navigate to the Service Bus Console at http://localhost:7001/servicebus.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s console tuas user jdoe to create a a 3. Using a different web browser, log in to the Service Bus S v new session. For this practice, call this console (fc 2. eTotsimulate his two different web browser a instances, you can open a private session s using the New Private Window ed inoFirefox u ñ option. a t st File >sNew e a a. In the Firefox browser, click Private Window. C cen z ue le li q s Vá ferab e ip rans l e F n-t no




c.

4.

Log in to the console with the jdoe/ See OracleServiceBus12cPassword File credentials.

d. In the top-right corner, click Create to create a new session. Create a concurrency conflict scenario. a. In console 1, click Resources in the left pane. b. You will use the same set of SB services that was available for Practice 04. Therefore, in the Target Navigation section, navigate to Practice_04 > Shipping > Business Services, and click LocalShippingService.




a


c.

Navigate to the Configuration > Transport tab.

d.

Use the drop-down to change the Load Balancing Algorithm to Random.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu e. Click Save. a S v is f. Navigate to the same location in console Select Random for the (f2c(Private hWindow). t a e d Load Balancing Algorithm, andethen click Save. us and click Activate. ñ a description a o g. In console 2, click Activate. Enter t t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no

h.

Return to console 1 and activate the session. Were you able to activate the session? If not, what message did you get? Hint: You should have received a message about a concurrency conflict.




i.

In the Conflicts tab, select LocalShippingService.

j.

To resolve the concurrency conflict, select the LocalShippingService, and click the Synchronize icon.

a s a )h ฺ l c ฺ el ide t n uif you need e help G k. Activate the session. Do not forget to add a description. Descriptions @ t n ezby other e to roll back, and when you are viewing sessions created users. u d q s tu l. Log out and close console 2 (Private Window). a S v (fc e this a ed o us 5. Resolve a conflict. ñ a st s1.e t a. Create a new session in console a C cetonPractice_04 >Shipping > Business Services. b. In Project Explorer, navigate z e lito LocalShippingService and click the Delete button. u box lnext q e c. Select thescheck Vá ferab e ip rans l e F n-t no

d.

Click Yes when prompted about the delete.




e.

f.

Notice that there is now a major conflict in the Conflict section. Click View Conflicts and expand ShippingService to see what is causing the problem.

Because LocalShippingService is being used by a pipeline service, you do not want to go ahead with the delete. Click Discard to remove the changes, and then click Discard when prompted.




a

Practice 5-2: Customizing a Service Bus Configuration


Overview In this practice, you use the find-and-replace functionality of the Service Bus Console to locate all the environment variables in the Service Bus configuration that match a certain value. This is useful when migrating Service Bus configurations to an environment that might be set up differently with different names, port numbers, and so on. You also create a customization file that can be repeatedly used to automatically do the find and replace on environment variables. This is particularly useful when frequently moving a configuration from a development to a testing environment. In this practice, you: • Find and replace environmental values in a Service Bus configuration • Create a customization file to automatically find and replace specific values • Execute a customization file

s a h 1. Change the port number of the WebLogic server in osb_domain to 7101.ฺcl) el ideฺ t a. Log in to the WebLogic Server Administration Console of osb_domain n u e G (http://localhost:7001/console) using the weblogic/ See @ t ez den OracleServiceBus12cPassword File credentials. u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no Tasks

a

b.

Navigate to osb_domain > Environment > Servers, and click AdminServer(admin) in the Summary of Servers section.

c.

In the Change Center, click Lock & Edit. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



d.

Change Listen Port to 7101.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e Fe. Save -t your changes, and then in Resources, click Activate Changes. You might be n o logged out automatically. If not, log out of the console. n f.

2.

Log in again to the WebLogic Administration Console at the new listen port to verify the change.

In the Service Bus Console, find and replace values for the Service Bus projects to reflect the new port number. a. Log in to the Service Bus Console for osb_domain by specifying the new port number in the URL (http://localhost:7101/servicebus) and using weblogic/ See OracleServiceBus12cPassword File.




b.

In Resources, navigate to Practice_04 > Shipping > Proxy Service and test the ShippingService proxy service.

c.

What happens when you test the service? Answer: You receive a connection error.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a d. Create a new session. C cen zthat e. To rectify the u error you e li received in the previous step, you need to change the port q e l number ofsthe Service Bus á erab services. Navigate to Admin > Configuration and select FindV and Replace. e nsf p i l Fe n-tra no




f.

Find the value 7001 and replace it with 7101. Click Replace.

s a h l) ฺ c ฺ g. Close the dialog box. l nte uide h. How many environment variables were changed? e @ nt G z Answer: 4 e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

i. j.

Activate your session. Do not forget to add a description. Retest the ShippingService proxy service. What happened this time? Answer: It executed without any errors.



a


3.

Create a configuration file to automate the find and replace capabilities. a. Return to the WebLogic Server Administration Console for osb_domain. (http://localhost:7101/console). b. Change the AdminServer Listen Port back to 7001, and then save and activate the changes.

c.

Return to the osb_domain Service Bus Console. Log in again using http://localhost:7001/servicebus. Note: You may need to log out of the Service Bus Console and completely close and reopen your Firefox browser to reset your login. This issue can occur because you have dynamically changed the port of the server. Create a new session. Navigate to Admin > Configuration and select Create Configuration File.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no d. e.



a


f.

On the Create Configuration File page, ensure that Practice_04 is selected and System is deselected, and then click Create.

g.

Save the customization file by selecting Save File and clicking OK. The file is saved as OSBCutomizationFile.xml in the Downloads folder. Close the Configuration window. Edit OSBCutomizationFile.xml in a text editor such as gedit or Emacs (right-click the file and select Open With > editor name), and replace all the instances of 7101 with 7001. Save and close the file after making the changes.

i.

Return to the Service Bus Console and navigate to Admin > Configuration and select Execute Configuration File.

s a h l) ฺ c ฺ l nte uide h. e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


j.

Browse to /home/oracle/Downloads and open the previously saved configuration file. Click Next.

k. Click Finish. Verify successful execution of the file. l. Activate your session, and add the description. m. Navigate to Resources > Practice_04 > Shipping > Proxy Service > and test the ShippingService proxy service.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C successfully. n. Verify that the testzruns en c e i l squ rable á V fe e s p i l n e a r F n-t no



a

Practice 5-3: Managing Service Bus Using WLST


Overview In this practice, you use a WLST script to manage some of the common administration tasks you might encounter with Service Bus. You edit a script that exports the Practice_04 project from osb_domain. Then you edit a script to import another project into osb_domain. This also includes creating and activating a session. To do this, you use SessionManagementMBean and ALSBConfigurationMBean. In this practice, you: • Export a configuration file in a WLST script • Create a session in a WLST script • Import a configuration file in a WLST script • Activate a session in a WLST script

a s a 1. Modify a WLST script to export a Service Bus configuration file. )h ฺ l c ฺ a. Open the /home/oracle/labs_SA/Practice_05/wlst/export el ide t n u Open with /wlstScript_export.py file in a text editor (right-click theefile and G click @ t Other Application, and then select a Text Editor.) ez den u q b. Add the appropriate code as instructed at the appropriate location tu in the file. You will as see comments for where to add each linefc ofvcode. is S ( e th a Note: Alternatively, you can replace the wlstScript_export.py file in the d s e u ñ /home/oracle/labs_SA/Practice_05/wlst/export directory with the already o tfrom sta sfile e edited wlstScript_export.py the a C cen /home/oracle/labs_SA/Practice_05/Solutions/wlst/export directory. If z e i l u you do so, q to Step le2 that follows. sskip b á a c. This V WLST script already set up to import the appropriate classes needed for er is Bus f e s p exporting a Service configuration to a JAR file. It is also set up to connect initially i n a r Fel tonthe t Administration Server in osb_domain. o n Tasks



d.

Use the findService method to obtain the ALSBConfigurationMBean Mbean for performing the read-only operations. Assign the MBean to a variable that can be used later. Add the following code to perform this task:


alsbCore = findService(ALSBConfigurationMBean.NAME, ALSBConfigurationMBean.TYPE) e.

Create a new Ref object that identifies the Service Bus project. Assign it to a variable: projectRef = Ref(Ref.PROJECT_REF, Ref.DOMAIN, "Practice_04")

f.

Add the Ref object to a new Java Collection. collection = Collections.singleton(projectRef)

g.

Export the Service Bus project using the export method of ALSBConfigurationMBean. Assign the result to the theBytes variable. theBytes = alsbCore.export(collection, true, None)

h.

Finally, add the code to disconnect from the current server:

a s a h ) following: l i. Save the file after making the changes. The edited file should look likeฺc the el ideฺ t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no disconnect()




2.

In a Terminal window, navigate to /home/oracle/labs_SA/Practice_05/wlst/export and execute the executeScripts.sh file to export the Service Bus configurations (the Practice_04 project) from the osb_domain to a JAR file.

3.

Verify that Practice_05_sbconfig.jar is created in the current working directory.

Note: The solution script for exporting a Service Bus configuration is provided in the /home/oracle/labs_SA/Solutions/wlst/export directory. In case you fail to create the configuration file correctly, use the script provided with the solutions. Optionally, you can view the contents of the file by right-clicking Practice_05_sbconfig.jar and selecting Open with "Archive Manager". Now you can view the contents of the exported project.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q u osb_domain. The s file tinto 4. Modify a WLST script to import a Service Bus configuration a S v fc this sample configuration file (which creates the (Sample_OSB_Project) is already provided a e with the script file. The script will also create s session and finally activate the session. ed oa unew ñ a a. Open the /home/oracle/labs_SA/Practice_05/wlst/import t st file insea text a /wlstScript_import.py editor. Add the appropriate code as instructed C cen z at the appropriate location in the file. You will see comments for where to add each line e e li u q l of code. s á erabyou can replace the wlstScript_import.py file in the VAlternatively, Note: f e s p i l n /home/oracle/labs_SA/Practice_05/wlst/import directory with the already a r Fe edited t wlstScript_import.py file from the n no/home/oracle/labs_SA/Practice_05/Solutions/wlst/import directory. If b.

c.

you do so, skip to Step 5 that follows. This WLST script is already set up to import the appropriate classes needed for importing a Service Bus configuration to a JAR file. It is also set up to connect initially to the administration server in osb_domain.

Use the findService method to get SessionManagementMBean. Assign the MBean to a variable that can be used later. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.


sessionMBean = findService(SessionManagementMBean.NAME, SessionManagementMBean.TYPE) d.

Use the MBean to create a new session called Import Session.


print '...Creating a new session...' sessionMBean.createSession("ImportSession") e.

Use the findService method to obtain ALSBConfigurationMBean for the new session. Append the name of the specific session to the MBean name. alsbSession = findService(ALSBConfigurationMBean.NAME + "." + "ImportSession",ALSBConfigurationMBean.TYPE)

f.

Use the uploadJarFile method of ALSBConfigurationMBean. Provide the variable that holds the SB configuration as the argument to this method. alsbSession.uploadJarFile(bytes)

a s a )h ฺ l c ฺ el ide t n u alsbSession.importUploaded(None) e G @ t ez of den h. Activate the session. Use the activateSession method u q u apply the changes. s session tand ALSBSessionManagementMBean to activateathe S v (fc e this print 'Activating the session...' a sessionMBean.activateSession("ImportSession", "Imported the ed o us ñ a project.") t t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no g.

Call the importUploaded method of ALSBConfigurationMBean. This method can take an import plan as input, but because you do not have one, you can use the keyword None instead.




i.

Save and close the file after making the changes. The edited portion of the file should look like the following:

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a 5. In a Terminal window, navigate stto se t a /home/oracle/labs_SA/Practice_05/wlst/import and execute the C cen z executeScripts.sh to limport i the Sample_OSB_Project project from the ue filelfile q e s sample_sbconfig.jar into osb_domain. á erab V Note: e The solution f script for importing a Service Bus configuration file is provided in the s p i l n /home/oracle/labs_SA/Practice_05/Solutions/wlst/import directory. In case e -tra Fyou nofailnto write the script correctly, use the script provided with the solutions.




6.

Return to the Service Bus Console for osb_domain. Navigate to the Project Explorer and confirm that the project, Sample_OSB_Project, exists.

a s a )h ฺ l c 7. Delete Sample_OSB_Project from osb_domain. ฺ el ide t n a. Click the Create button to start a new session. u e G @ t z nothing b. In Resources, select Sample_OSB_Project (ensureethat nelse is selected) e u d and click Delete. q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

c. d.

Click Yes in the confirmation window. Click Activate, enter a description, and then click the Activate button to activate the changes.



(Optional) Practice 5-4: Propagating a Service Bus Configuration


Overview In this practice, you export a Service Bus configuration from the current domain and import it into a new Service Bus domain called prod_domain. This is an example of moving from a development environment to a testing or production environment. In this practice, you: • Export a configuration file • Import a configuration file

Tasks 1. Set up the practice environment. a. In a Terminal window, execute the following command to create a new PROD1 prefix. $ cd /home/oracle/labs_SA/Practice_05/create_schema $ ./create_schema.sh

a s a ) h ฺ3-3. l b. Create a new SB domain called prod_domain using the instructions ฺin Lesson c eland 8091 Use PROD1 for the schema, 7091 for the admin server port number, t idefor the n u e OSB managed server. G @ t z n e 2. Start the Administration Server and the Service Bus Managed Server in prod_domain. e squ Stud a. Open a new Terminal window and navigate v toathe /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/domains/prod_do (fc e this a main/bin directory. ed o us ñ a b. Start the Administration Server t the following command (all on one line): st bysexecuting e a C-–title $ gnome-terminal en "ProdAdminServer" –e ./startWebLogic.sh z c e i l If prompted,qenter leadministrative credentials: weblogic/welcome1. s u rathe b á Note:VThis command the server in a separate Terminal window with the e so thatstarts f e s p appropriate title you do not confuse it with other server Terminal windows. You i n a r Fel can t also start it using a separate terminal window with just the ./startWebLogic.sh n o command. n c.

It will take a couple of minutes to start up. Make sure you see the message "Server started in RUNNING mode" to confirm that the Administration server is running. Similarly, start the Service Bus Managed Server. From the /u01/app/oracle/product/fmw/12.1.3.0/user_projects/domains/prod_ domain/bin directory, execute the following command: $ gnome-terminal -–title "ProdServiceBusServer" –e "./startManagedWebLogic.sh osb_server1" When prompted, enter the administrative credentials: weblogic/ See OracleServiceBus12cPassword File.




Note: You can also start it using a separate terminal window with just the ./startManagedWebLogic.sh osb_server1 command. It will take a couple of minutes to start. Make sure you see the message "Server started in RUNNING mode" to confirm that the SB managed server is running. 3.

Export the configuration file. a. In a web browser, navigate to the Service Bus Console for the original domain (osb_domain) at http://localhost:7001/servicebus. Log in as weblogic/ See OracleServiceBus12cPassword File. b. c. d.

Navigate to the Resources section of the Service Bus Console. Select Practice_04. Click the Export button.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e li box, ensure that Practice_04 is selected and System uResources q e e. In the Export dialog l s á erab is notV selected. f e s p i l n Fe n-tra no




f.

Click Export and click OK to save the file. The file, named sbconfig.jar, will be saved to your Downloads folder.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ 4. Import the configuration file into prod_domain. a e to t s a a. Start the Service BusCConsole forsprod_domain by navigating to en in a web browser. z http://localhost:7091/servicebus c e i l qu ble b. Log in as s weblogic/welcome1. á ra V a newfesession. c. Create e s ip ranto the Resources section of the Service Bus Console. Fd.el Navigate -t n o n



a


e.

Click the Import button.

f.

Browse to the location where you saved the Service Bus configuration JAR file, sbconfig.jar, and open the file. Click Next.

s a h l) ฺ c ฺ l nte uide e @ nt G z e qu SClick udeImport. g. Ensure that the Practice_04 configuration filea issselected. t cv this f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

h.

Activate the session. Do not forget to add a description and click Activate.



a

5.

Validate the changes to prod_domain. a. In the prod_domain Service Bus Console, navigate to Project Explorer.


b.

Expand Practice_04 > Notification > Pipeline and click ConfirmationEmailQueue_pipeline.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ staopensethetoTest Console for c. In the Folder Definition a pane, C cen z e ConfirmationEmailQueue_pipeline by clicking the test button. u le li q s d. In the Payload rab change CustomerID and OrderID to 3. Vá fesection, e ip rans l e F n-t no



a


6.

e.

Execute the test to ensure that the proxy service is running as expected. There should be no errors. However, no response is expected because this is a one-way service.

f.

Close the Test Console.

Propagate a configuration change from one domain to the other. a. Return to the Service Bus Console of osb_domain. b. Create a new session. c. Navigate to Project Explorer. d. Expand Practice_04 > Notification > Pipeline. Click the ConfirmationEmailQueue_pipeline.

s a h l) ฺ c ฺ l nte uide e @ nt G z e e u tu>dGeneral q s e. On the Pipeline Definition section, click the Configuration tab. a is S v c f ( e th a d ñe to us a t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no



a


f.

Supply a description for the pipeline proxy service, and then click the Save

g.

Click Activate and enter a description.

button.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a h. Export the Practice_04 project. ed s uneed ñ 3 if tyou a o t Hint: View the instructions in step a reminder. s se a C cen z e u le li q s á erab VThe Note: configuration file, named sbconfig(1).jar, is saved to the Downloads f e s p i l n folder. Fe n-tra no 7. Verify that the changes to the service reflect successfully in prod_domain. a.

Return to the prod_domain Service Bus Console.

b.

Create a session. Note: You will be prompted to log in again so there is no confusion between the two Service Bus Consoles. Import the sbconfig(1).jar file.

c.

d. e.

Activate the session. Confirm that the new description of the ConfirmationEmailQueue_pipeline service is visible in prod_domain. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



f. 8.

Log out of the Service Bus Console for prod_domain and close the browser window.

Shut down the Administration Server and Service Bus Managed Server in prod_domain. a. Return to the Terminal windows that are executing the Administration Server and Service Bus Managed Servers for prod_domain (ProdAdminServer and Prod Service Bus Server). Important: Ensure that you are not shutting down the osb_domain server. b. Enter the “Ctrl + C" key combination in each Terminal window to shut down the servers. c. Close the Terminal windows after the servers stop.




a



The solution files contain the completed Practice 5-3 WLST scripts for you to execute and verify the result of importing and exporting Service Bus configuration files by using the command-line tool. There are no solutions for Practices 5-1 and 5-2, and Practice 5-4 is optional. These practices are not required to be completed for any subsequent practices.

Assumptions •

The Practice_04 project is deployed on the Service Bus server (performed in Practice 4-1).

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen Tasks z e u le li q 1. Navigate to /home/oracle/labs_SA/Practice_05/Solutions/wlst/export and s b á a V fer run the executeScripts.sh file to export the Service Bus configuration file. e s p i 2. Verify the el that anexport file Practice_05_sbconfig.jar was created in r F/home/oracle/labs_SA/Practice_05/wlst/export. t non you can view the contents of the file by right-clicking Optionally, 3. 4.

Practice_05_sbconfig.jar and selecting Open with "Archive Manager." Now you can view the contents of the exported project. Navigate to /home/oracle/labs_SA/Practice_05/Solutions/wlst/import and run the executeScripts.sh file to import the Service Bus configuration file. Perform steps 6 and 7 in Practice 5-3 to verify that the new project was created and then to delete the new project.




s a h l) ฺ c ฺ l nte uide e G6: @ t Practices for Lesson z n e u andtuMonitoring de q Reporting s va his S c f ( aChapterse6 t d e añ e to u t s Ca cens z ue le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 6: Reporting and Monitoring Chapter 6 - Page 1

a



Practices Overview In the practices for this lesson, you: • Monitor the health of Service Bus services • Define Service-Level Agreements • Analyze Service Bus Reports




a

Practice 6-1: Monitoring Service Health


Overview In this practice, you take advantage of the Dashboard found within the Service Bus and Fusion Middleware Control Consoles. The Dashboards give you the ability to monitor the performance and health of individual services and their operations or of the entire service bus. However, to monitor a service, you must first configure Service Bus to collect statistics for it. You will monitor the supplied OrderManagementService_proxy, which simply passes incoming requests through to OrderManagementService that is deployed to the Service Bus Domain.

Assumptions •

Oracle Service Bus 12c 12.1.3.0 is installed and is running for osb_domain.

•

The web service applications used by the Service Bus services are deployed and running on Oracle WebLogic server.

a s a Tasks )h ฺ l c ฺ l Console. 1. Import the sample Service Bus project by using the Fusion Middlewarete Control de i n u e a. In Target Navigation, right-click SOA > servicebus(AdminServer) Gselect Import. @ nand t z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

b.

On the Import Resources page, click the Browse button that is next to Jar Source, browse to /home/oracle/labs_SA/Practice_06, and open the sbconfig.jar file. Click Next.




c.

Review the contents of the Jar file to be imported, and then click Finish.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no d.

a

Ensure that you see the message “The import was completed successfully.” Close the window.




e.

2.

Refresh the page Navigation.

, and then verify that the project is visible in the Target

Configure monitoring for a proxy service. a. First ensure that the Global Settings are enabled. In Enterprise Manager, select SOA > servicebus(AdminService). b. Select the Global Settings tab, and verify that all options are selected.


c. d.

In the Target Navigation, expand SOA > service-bus(AdminService) and select Practice_06. Click the Operations tab.



a


e.

Select the OrderManagementServicePipeline.

f. g.

Select the Properties tab. Ensure that Monitoring is enabled, Monitoring Level is Pipeline, and Aggregation Interval is 3 min.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s h. Click Apply. cva this S f ( da use e 3. Launch the Test Console for OrderManagementServicePipeline. ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e t Include Tracing is selected. 4. FEnsure that n o n

5.

a

In the Test Console, execute two test cases for the getOrdersForCustomer operation and the getOrderStatus operation each. Test both the operations, once with valid data and once with invalid data. This generates statistics that you will view later. a. Test the getOrdersForCustomer operation with valid parameters. Select getOrdersForCustomer from the Available Operations drop-down list at the top, and then enter the following payload values: : Tom : 1001 : Harkey Click Execute. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



b. c.

Click Back. Test the getOrdersForCustomer operation again with invalid parameters. Enter the following payload values: : No : 99

a s a Click Execute. You will see an error message in the Response Document, h as ) such l c “The invocation resulted in an error.” ฺ ฺ l e e t d i n d. Click Back. u e G @ t e. Test the getOrderStatus operation with a valid parameter. Select n ez list, e u d getOrderStatus from the Available Operationsq drop-down and then enter the u s t a S following payload value: cv this f ( : 1001 da use e ñ Click Execute. sta se to a f. Click Back. C cen z g. Test the getOrderStatus e li operation again with invalid parameters. Enter the u q e l following s payload value: b á ra99 V : e f e s You will see an error message in the Response Document, such as ipClick Execute. l n e a r F “The -tinvocation resulted in an error.” n o n : Body

h.





6.

Monitor the service statistics. a. In the Enterprise Console Target Navigation, right-click service-bus(AdminServer) and select Home > Service Health.

b.

Click Search for a list of Services.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a c. Click the OrderManagementServicePipeline ed o us in the table under Services. ñ a t the eService t Metrics table. You will find the Failure Ratio d. Record the following datasfrom a s by clicking within theC Services section: en z c e i l Field Value squ rable á V Overall e Avg. f e s p i n Time Fel n-traResponse Message Count no Error Count

Failure Ratio e.

If no data is available, the three-minute aggregation interval may have already elapsed. Run the client application test and switch to Since Last Reset in the Search section.



Practice 6-2: Defining Service-Level Agreements


Overview In this practice, you configure Service-Level Agreements (SLAs) on an existing proxy service. An SLA triggers alerts when their conditions have been met. The OrderManagementService SLA tracks the number of errors that occur and also the service’s response time. For the purposes of this practice, alerts from either SLA will be delivered to a JMS destination that is deployed to Service Bus Domain (although typically the destination would be some centralized operations center). In this practice, you: • Configure a JMS alert destination • Assign an SLA to a proxy service • Monitor alerts triggered from an SLA

Tasks 1.

a s a )h ฺ l c ฺ el ide t n u e Factory G @ b. Execute the create_jms.sh script to create a JMS Connection and JMS t z n e e u Queue within the osb_domain domain. You will see the following message if the script d q u s t is executed successfully. cva this S f ( da use e ñ ta e to s a c. Launch the WebLogic Administration Console for the osb_domain domain CServer ns e z c e (http://localhost:7001/console) using the (See OracleServiceBus12cPassword li squ rable File) á credentials. V fe e s p i l n e a r F n-t no Create a JMS Connection Factory and Queue and log their JNDI names. a. Open a Terminal window and navigate to the /home/oracle/labs_SA/Practice_06/resources directory.




d.

Confirm that AlertQueue and AlertConnectionFactory were successfully deployed by navigating to Services > Messaging > JMS Modules and clicking jmsResources in the JMS Modules table.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ a e to stthe a e. Record the JNDI names of s resources: C cenfollowing z Resource e JNDI Name i l u q e l AlertQueue ás erab V f e AlertConnectionFactory s p i l n Fe n-tra no 2.

a

Configure SLA Alerts for the OrderManagementService_proxy Proxy Service. a. In the Fusion Middleware Control Console Target Navigation section, expand SOA > Service Bus > Practice_06. b. Click the Operations tab. c. Select the options to enable SLA Alerts and Pipeline Alerts. Make sure the Aggregation Interval is set to 3 minutes, and then click Apply.

d. e.

Click the OrderManagementService_proxy. Select the Properties tab. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



f.

Select the Enabled check box for Monitoring and SLA Alerting. Make sure the Aggregation interval is set to 3 Mins.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a g. Click Apply. C cen z e u le li q s 3. In the Service á Buseconsole, ab create a JMS alert destination. r V f e a. ip Create a new s Service Bus session. l n e a r Fb. Innthe -t Resources tab, right-click the Practice_06 project and select Create > Folder. o c.n In the Create a New Folder Resource Name field, enter Alerts. Click Create.




d.

Right-click the Alerts folder and select Create > Alert Destination.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a tenter JMSAlertDestination for Resource st dialog, e. In the Create Alert Destination e a s C cen Name. z e u le li f. Click Create. q s á erab V f e g. p In the Alerts Destination Definition > JMS Destination section, click the Add button i l n e a to add the JMS Destination. r F n-t h. o the JMS JNDI names recorded earlier, enter the full Destination URI. Recall that n aUsing JMS URL is of the form jms://://

Hint: Use Localhost for and 7003 for . Use the JNDI name recorded earlier for the AlertQueue and AlertConnectionFactory options.




i.

For Message Type, select Text.

s a h l) ฺ c ฺ l nte uide e j. Click OK. Your Alert Destination page should look like the following:t G @ z n e e u d q s tu a S v (fc e this a ed o us ñ a st se t a C cen k. Click the Save button. z e li a description. l. Activate theqsession include u and e l s Vá ferab e s based on error count. 4. Define rule ip an rSLA l n e a Fa. Create -t a new session. n o b.n In Resources, click Practice_06 > Proxy Service, and then click c. d. e.

OrderManagementService_proxy. Click the SLA Alert Rules tab.

Click the Add button. In the Create SLA Alert Rule dialog box, enter or select the following information: Field Value Name Order Error Count Rule Description Summary

f.

a

Trigger an alert when at least 2 errors occur

OrderManagementService error count SLA violated Severity Critical For Alert Destination, click the Search button, select JMSAlertDestination, and then click Next.




g.

Set the Condition Aggregation Interval for this SLA to 3 minutes.

h. i.

Click the Add button to add open the Condition Builder. In the Condition Builder, enter the following:

s a h l) ฺ c ฺ l j. Click the Update Condition button. nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t o n k. Click Create, and then click the Save button to save the new SLA.



a


5.

Define an SLA rule based on response time. a. Make sure the pipeline monitoring level is set to Pipeline level. You can verify this by clicking the Operations tab in Enterprise Manager.

b.

Click the SLA Alert Rules tab in the Service Bus console.

c. d.

Click the Add button . Enter or select the following information: Field Value Name Order Response Time

a s a )h ฺ l c ฺ Rule Description Trigger an alert when response time is greater el thanide t n 1ms u e G @ t nSLA Summary OrderManagementService response ez dtime e u q violated s tu a S v Severity Major (fc e this a e. Set the Alert Destination to JMSAlertDestination (as you did before in step 4f.) ed o us ñ a f. Click Next. st se t a C tocadd enopen the Condition Builder. z g. Click the Add button e i l le enter the following: h. In the Condition squ raBuilder, b á V fe e s p i l n e a r F n-t The aggregation interval should be 3, which is the same for the service noNote: monitoring and SLA alerts.

6.

i.

Click Create.

j. k.

Click the Save button to complete the SLA Alert. Activate your changes, enter a description, and click Create.

Test the SLA alerts. a. Launch the test console for OrderManagementService_proxy. b.

Under Available Operations, select getOrderStatus.




c.

In the Payload field, locate the element. Set its value to 99. This causes the service to return an error because the supplied ID is invalid.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu d. Click Execute. a S v c error. e. Repeat the previous steps to generate a(fsecond his t a e f. Execute a third test using a correct edID ofo1001. us ñ a t g. Close the Test Console. st Ca cense z li in the Fusion Middleware Control Console. uethe dashboard 7. View the alerts using q e l s á eNavigation, a. Under rab click service-bus (AdminServer). VTarget f e s and then the SLA Alerts tab, if it is not already visible. If you do not b. lip Click Dashboard, n e a r F see t SLA Alerts, click Refresh on your browser. -the n o n Note: You might have to wait for up to 3 minutes for this to display. If you still cannot see the alerts, double-check your configuration settings. Did you set the aggregation interval for your Alert Rule to 3 minutes, or is it still set to the default of 10 minutes?




s a h l) ฺ c ฺ l c. te uide n e d. @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no Note: If your response time is very fast, you may not see a major alert for Order Response Time. Click an area of the pie chart to filter the alerts being displayed. Locate the Alert Name column. Click one of the alerts to view its details.



a

Practice 6-3: Analyzing Service Bus Reports


Overview In this practice, you use OrderManagementService_proxy to generate and view sample Service Bus reports. The Proxy Service extracts the order status information of any given order, and generates a report. These reports give relevant information when tracking order processing. In this practice, you: • Use a proxy service to trigger reports • View reports using the Service Bus console

Tasks 1.

Enable the OrderManagementServicePipeline report option. a. In Enterprise Manager Target Navigation section, click Practice_06. b. Click the Operations tab. c. Select to enable the Reports option for the Pipeline.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e d. Click Apply. ñ sta se to a C inspect enthe report action in the Proxy Service Pipeline’s z 2. In the Service Bus console, c e i l Message Flow. qu s rable á a. ClickV the VieweMessage Flow icon for OrderManagementServicePipeline. f e s p i l n Fe n-tra no



a


b.

Click the getOrderStatus operational branch for which the reporting action is configured.

a s a )h ฺ l c ฺ el ide t n u e G @ t c. Click the RouteTo_getOrderStatus node and select n ezViewdRoute. e u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t d.no Click the Report action in the message flow. It extracts the order status information from the service’s response. Note that this action executes an XPath expression to construct the body of the custom report:

e. 3.

Note: You can also create an XSLT transformation to extract data into a report. Similarly, the key name specifies the order ID. Click Close.

Test the proxy service. a. Launch the test console for OrderManagementService_proxy. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



b.

4.

c.

In the Payload field, locate the element. Set its value to 1001, and click Execute. Repeat the previous step with the 1002 value.

d.


View the reports from the Fusion Middleware Control Console. a. In Target Navigation, right-click service-bus(AdminServer) and select Message Reports.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ ta e to s a s All Dates. Search reports usingC the default nsetting e z c ue le li q s Vá ferab e ip rans l e F n-t no b. Click a Report Index to view a report’s contents.



a


c.

Scroll down and select the View Report Details option.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s b rabody Vtheácustom d. View of the report. e f e s p i Fel n-tran no e.

Click OK to close the report details.



a


Solution Instructions If you could not complete any of the practices successfully or you did not have the time to perform them, follow these instructions to apply the solution for each practice. To import a solution file in the Service Bus console: a. Create a new session b. Navigate to Resources > Import Resources c. Browse to open the solution jar file d. Click Next, and then Import e. Click Activate and then Create to deploy your changes Solution 6-1 1. Import the solution_6_1_sbconfig.jar configuration file located in the /home/oracle/labs_SA/Practice_06/Solutions directory. Note: If you started the practice, you must delete the Practice_06 project in the Service Bus console before importing the solution. If the project already exists in Service Bus, there might be a conflict of resources. Optionally, execute Tasks 3 to 6 of Practice 6-1 to test the proxy service and monitor statistics.

a s a )h ฺ l c ฺ 2. el ide t n u e G @ t ez den u q s tu a S Solution 6-2 v is JNDI names. (fcandelogththeir 1. Create a JMS Connection Factory and Queue, a ed oto the us a. Open a Terminal window and navigate ñ a t t /home/oracle/labs_SA/Practice_06/resources directory. as nse C z licescript to create a JMS Connection Factory and JMS b. Execute the create_jms.sh e u Queue within the osb_domain domain. You will see the following message if the script le sqsuccessfully. b á a is executed V fer e s p i l n e a r F n-t no

2.

3.

Import the solution_6_2_sbconfig.jar configuration file located in the /home/oracle/labs_SA/Practice_06/Solutions directory.

Note: If you started the practice, or completed the previous practice, you must delete the Practice_06 project in the Service Bus console before importing the solution. If the project already exists in SB, there might be a conflict of resources. Optionally, execute Tasks 6 and 7 of Practice 6-2 to test and view the alerts.




Solution 6-3 1. Import the solution_6_3_sbconfig.jar configuration file located in the /home/oracle/labs_SA/Practice_06/Solutions directory.

2.

Note: If you started the practice, or completed the previous practice, you must delete the Practice_06 project in the Service Bus console before importing the solution. If the project already exists in Service Bus, there might be a conflict of resources. Optionally, execute Tasks 3 and 4 of Practice 6-3 to test the proxy service and view the reports.




a





a


s a h l) ฺ c ฺ l nte uide e G7: @ t Practices for Lesson z n e u Security de q u Service Bus s t va his S c f ( aChapterse7 t d e añ e to u t s Ca cens z ue le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 7: Service Bus Security Chapter 7 - Page 1

a



Practices Overview Pega Corporation virtualized its Credit Card validation service (Java EE Web service) by using Oracle Service Bus to meet the increasing order processing demand. Pega Corporation has already added several other credit validation providers in order to meet the increased demand. Each credit validation provider has different authentication requirements. Pega Corporation decided to use Oracle Service Bus to mediate security. Pega Corporation has standardized on UserNameToken as the corporate authentication protocol. CreditCardService_Proxy proxy service on Service Bus requires UserNameToken-based authentication. To test the security implementation, you use the Service Bus Test Console. You use the Test Console to provide credentials (username/password) to authenticate the CreditCardService_Proxy proxy service. The identity of the authenticated user in Service Bus will be propagated to the CreditCardValidationService web service by using SAML. After this practice is complete, the execution flow will look as follows:




a


In the practices for this lesson, you will perform the following: • Configure and set up Oracle WSM and Oracle Service Bus security environment by creating the identities. • Configure and invoke a proxy service requiring User Name Token authentication. • Propagate identity of the authenticated user from Oracle Service Bus to the web service application by specifying a SAML Oracle WSM Service Policy.




a

Practice 7-1: Configuring the Security Environment Overview


In this practice, you configure Oracle WSM security by configuring the identities.

Assumptions •

Oracle Service Bus 12c 12.1.3.0 is installed and is running for the osb_domain.

•

Oracle Web Services Manager is enabled and configured to work with Service Bus.

•

CreditCardValidationService web service application is deployed and running on Oracle WebLogic server.

Tasks 1.

Create a user in WebLogic Server (WLS) by using Enterprise Manager. The Service Bus proxy service uses the WLS default authenticator to authenticate the username and password in the WS-Security SOAP Headers received from the client. The user created using Enterprise Manager is available to the WLS default authenticator. a. In Enterprise Manager, right-click osb_domain and select Security > Users and Groups.




a


b.

In the Users and Groups page, click Create.

c.

Create a user by specifying the following, and then click Create: User Name: joe

s a h l) ฺ New Password: See OracleServiceBus12cPassword File c ฺ l Confirm Password: See OracleServiceBus12cPassword File nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no 2.

a

Add a csf-key for the user joe in Enterprise Manager. This step is required for the Service Bus Test Console to look up the username and password using the csf-key. a. In Enterprise Manager, expand WebLogic Domain, and click osb_domain.




b.

In the osb_domain page, from the WebLogic Domain drop-down menu, click Security > Credentials.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s á erab VCreate c. Click fMap. e s p i l n Fe n-tra no



a


d.

Add the following name: oracle.wsm.security and click OK.

e.

Select the oracle.wsm.security map and click Create Key.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e s Key page, specify the following options and then click OK. f.elip In the Create n a r F Map: -toracle.wsm.security n o n Key: joe-key Type: Password User Name: joe (same as entered in Service Bus Console) Password: See OracleServiceBus12cPassword File (same as entered in Service Bus Console) Confirm Password: See OracleServiceBus12cPassword File



a


You should see the message: “The credential key, joe-key, has been created.” Expand oracle.wsm.security and you should see joe-key.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no g.



a

Practice 7-2: Applying a Security Policy to Proxy Services Overview


In this practice, you add oracle/wss_username_token_service_policy Oracle WSM policy, at run time to the CreditCardService_Proxy proxy service by using the Service Bus Console.

Tasks 1.

Import the sample Service Bus project by using the Service Bus console. a. In Service Bus Console, create a new session. b. In the Resources tab, click Import Config Jar.

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v c. On the Import Config Jar page, browse (and fc navigate histoand open the sbconfig.jar t a /home/oracle/labs_SA/Practice_07 directory, e ed o us ñ file. Click Next. a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no




d.

On the Import Config Jar > Input Configuration page, click Import.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ tothe import was successful, and then click staindicating e e. You should see the message a C cens Close. z lian appropriate description. ue lwith q e f. Activate the changes s Vá ferab e sToken Service Oracle WSM policy to the proxy service. ipUser rName l n 2. Add e a Fa. Create -t a new session in Service Bus. n o n b. Expand Project Explorer, and click Practice_07 > Proxy Service. c.

On the Proxy Service page, click CreditCardService_Proxy.



a


d.

On the Proxy Service Definition page, click the Security tab.

a s a e. Under the Security tab, select From OWSM Policy Store, and then click Attach )h ฺ l c Policies. ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e Ff. Innthe -t Security Policies – CreditCardService_Proxy dialog box, enter o n oracle/wss_username_token_service_policy in the Name field, and then click Search.




g.

Select oracle/wss_username_token_service_policy, and then click Attach.

h.

Verify that the policy is attached, and then click OK.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s b Activate the session with an appropriate description. á eraand i. SaveV the changes f e ip rans l e F n-t no



a

Practice 7-3: Testing the Proxy Service Security Implementation


Overview In this practice, you perform a positive test and a negative test to confirm the Oracle WSM security (User Name Token policy) implementation on the proxy service by using the Service Bus Test Console.

Assumptions • • • •

The Oracle WSM security environment is configured to protect Service Bus services. Respective Oracle WSM key is defined. Respective user identities are created in Oracle WebLogic Server. The Service Bus proxy service is secured with the oracle/wss_username_token_service_policy Oracle WSM policy.

a s a 1. Perform a positive test to verify that the proxy service is securely invoked successfully. )h ฺ l c ฺ a. In Service Bus Console, navigate to the Practice_07 > Proxy Service folder. el ide t n u for the b. Click the green arrow button in the Actions section to launch the Test Console e G @ t CreditCardService_Proxy proxy service. ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e values in the Payload field. Specify the card number as Fc. Innthe -t Test Console, enter and o 1234-1234-1234-1234 the card type as AMEX as shown in the screenshot n Tasks

below. Because the CreditCardService_Proxy proxy service is attached with the User Name Token Oracle WSM policy, you notice a Security section in the Test Console with an oracle/wss_username_token_client_policy policy name and with a csf-key property.




d.

In the Test section, specify joe-key as the override value. The username and password have already been created, and a mapping joe-key csf-key with the same credentials has already been created by using the OEM Console.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s á etoratestb the proxy service. VExecute e. Click f e s p i l n ra see the following response (in addition to SOAP headers). Ff.e You tshould n no

g.




a


2.

Perform a negative test by modifying the password of user joe to a different value, and then invoking the proxy service. a. In Enterprise Manager, right-click osb_domain and select Security > Users and Groups.




a


b.

On the Users and Groups page, click joe.

s a h l) ฺ c ฺ c. On the “Settings for User: joe” page, click the Passwords tab. l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


d.

Modify the password to (See OracleServiceBus12cPassword File), and then click Save.

s a h e. Execute the same test case (the one you performed for the positive test) l)using the c ฺ l eฺ Service Bus Test Console. You see the request fail with the following e response, t d i n uMap. e Credential because joe’s password does not match the value used in the G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s b á erofauser 3. Reset e theV password joe back to (See OraScleServiceBus12cPassword f s p i el -tran FFile). non



a

Practice 7-4: Propagating Identity from Service Bus to Secured Web Service


Overview In this practice, you propagate the identity of the user authenticated in Oracle Service Bus to the web service application. As a part of this practice, you perform the following steps: • Protect the CreditCardValidationService Java EE web service application deployed to the WebLogic Server by using the oracle/wss10_saml_token_service_policy service Oracle WSM policy. • Update and attach the CreditCardService business service in Oracle Service Bus with the oracle/wss10_saml_token_client_policy client Oracle WSM policy. • Test the security implementation.

Assumptions

a s a )h ฺ l c ฺ • The password of user joe is reinstated to See OracleServiceBus12cPassword el ide t n File. u e G @ t ez den Tasks u q s tu a S 1. Add a SAML service Oracle WSM policy to the CreditCardValidationService web v s c i f ( h service application. e t expand WebLogic Domain > da usManager, a. In the Target Navigation panelñ ofeEnterprise osb_domain and click AdminServer. sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no •

The CreditCardService_Proxy proxy service is secured with the User Name Token Oracle WSM policy.




b.

On the AdminServer page, from the WebLogic Server drop-down menu, click Web Services.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use c. On the Web Services page, clickeCreditCardValidationPort. ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


d.

On the Web Service Endpoint page, select WSM Policies tab, and click Attach/Detach.




a

e.

On the Attach/Detach Policies page, select oracle/wss10_saml_token_service_policy and click Attach.


Note: You need to filter by entering the policy name or scroll down to select this policy.




a


f.

On the Attach/Detach Policies page, verify that the policy is attached and click OK.




a


g.

You should see the policy information attached to the service.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no 2.

a

Test the security implementation by invoking the CreditCardValidationService web service from the Service Bus service without implementing the appropriate OWSM clientside policy. a. In Service Bus Console, navigate to the Projects > Practice_07 > Pipeline page.




b.

Click the green arrow button in the Actions section to launch the Test Console for the CreditCardServicePipeline.

c.

In the Test Console, enter values in the Payload field. Specify the card number as 1234-1234-1234-1234 and the card type as AMEX as shown in the screenshot below. Make sure the “Include Tracing” option is selected.


d.

Click Execute to test the pipeline. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.


a


e.

You should see the following invalid security message in the Invocation Trace section. This indicates that the Service Bus service didn’t have the required security infrastructure to invoke the secured web service application.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s va his S c f ( f. Close the Test Console. a se t d e ñ to u a t s 3. Add a SAML client Oracle WSM a policy stoe the CreditCardService business service. C n e z a. In Service Bus Console, e e create ic a new session. l u q l b. Navigate s b > Business Service and click CreditCardService. á to Practice_07 a r V e nsfe p i l Fe n-tra no

c.

On the Business Service Definition page, click the Security tab.



a


d.

Select From OWSM Policy Store, and click Attach Policies.

e.

Under Available Policies, enter oracle/wss10_saml_token_client_policy in the Name field, and click the search icon.

a s a )h ฺ l c ฺ el ide t n u and click e f. In the results table, select oracle/wss10_saml_token_client_policy G @ t ez den Attach. u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no




g.

In the Directly Attached Policies panel, verify that the policy is attached and click OK.

h.

Save and activate the changes with an appropriate description.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ 4. Test the security implementation. ta e to s a s a. In SB Console, navigate > Proxy Service page. C to ctheenPractice_07 z e i l squ rable á V fe e s p i l n e a r F n-t no



a

b.


c.

Click the green arrow button to launch the Test Console for the CreditCardService_Proxy proxy service. In the Test Console, enter values in the Payload field. Specify the card number as 1234-1234-1234-1234 and the card type as AMEX as shown in the screenshot below. In the Security section, specify joe-key as the override value for the oracle/wss_username_token_client_policy policy with the csf-key property.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t d.no Click Execute to test the proxy service.



a


e.

You should see the following response (in addition to SOAP headers). This indicates that the service was successfully invoked by using SAML identity propagation.

f.





a



Assumptions The solution file only contains the Service Bus security configurations. It does not contain configurations to secure the CreditCardValidationService Java EE web service application. Therefore, the solution file depends on: • Successful completion of Practice 7-1 • Successful completion of Task 1 of Practice 7-4 – Add a SAML service Oracle WSM policy to the CreditCardValidationService Web service application

Tasks 1.

In the Service Bus console, import the configuration file, solution_7_sbconfig.jar, provided in the /home/oracle/labs_SA/Practice_07/Solutions directory. Note: If you already partially completed the practices and created the Practice_07 project, then you must delete the existing Practice_07 project from the Service Bus Console before importing the solution file. Execute Task 4 of Practice 7-4 to test the security implementation.

s a h l) ฺ 2. c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no



a


a s a )h ฺ l c ฺ el ide t n u e G @ t Practices for n 8: ez Lesson e u d q Service s BusSHigh tu Availability a v (fc e8 this Chapter a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no


Practices for Lesson 8: Service Bus High Availability Chapter 8 - Page 1



Practices Overview Pega Corporation virtualized most of its back-end services (Java EE web service) by using Oracle Service Bus to meet the increasing order processing demand. It needs to create provisions for handling the large traffic on the services, and also to minimize the service down time. Service Bus is a proven, lightweight SOA integration platform, designed for connecting, mediating, and managing interactions between heterogeneous backend services, messaging services, and legacy endpoints. The purpose of this practice is to provide the detailed steps of architecting and implementing Service Bus for high availability that is critical for a missioncritical production deployment. In this practice, you create a new Service Bus domain (ServiceBusClusterDomain) that consists of an administrative server and two clustered managed servers. You then test the load balancing and failover capabilities. The backend service application (CreditCardValidationService) is deployed on to the services domain. For simplicity of the practice, you use the osb_domain as the services domain. You can view the architecture as follows:




a

Practice 8-1: Creating a Service Bus Cluster


Overview In this practice, you run the RCU script to create a new schema, and then you use the Oracle Fusion Middleware Configuration Wizard to create a Service Bus domain and configure a Service Bus cluster.

Tasks 1.

Navigate to the Practice_08 folder and run the script to create a new schema PROD2. Open a Terminal window, navigate to the /home/oracle/labs_SA/Practice_08/create_schema directory. Enter the following command to run the RCU utility: $ ./create_schema.sh

2.

Start the Oracle Fusion Middleware Configuration Wizard by entering the following commands in a Terminal window:

4.

Click Next.

a s a $ cd /u01/app/oracle/fmw_admin/12.1.3.0/oracle_common/) h l c common/bin ฺ l eฺ e t d $ ./config.sh i n u e G @ t 3. In the Domain Location field, leave the directory the same except n base_domain ez replace e u d with ServiceBusClusterDomain_domain. q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s Vá ferab e ip rans l e F n-t no




5.

Choose the templates. a. Select Create Domain Using Product Templates. b. Check the following available templates: − Oracle Service Bus – 12.1.3.0 [osb] − WebLogic Advanced Web Services for JAX-RPC Extension – 12.1.3.0 [oracle_common] − ODSIXQuery 2004 Components – 12.1.3.0 [oracle_common] − Oracle Enterprise Manager – 12.1.3.0 [em] − Oracle WSM Policy Manager – 12.1.3.0 [oracle_common] − Oracle JRF – 12.1.3.0 [oracle_common] − WebLogic Coherence Cluster Extension – 12.1.3.0 [wlserver] c. Click Next.


6.

a

In the Application Location screen, verify the domain name and location. Domain name: ServiceBusClusterDomain_domain Domain location: /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/domains Application location: /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/applications/Servi ceBusClusterDomain_domain




a s a )h ฺ l c ฺ el ide t n u e G @ t ez den 9. Click Next. u q s 1.7.0_71/usr/java/jdk1.7.0_71 tu 10. Select Production for Domain Mode and Oracle HotSpot for a S v s c i f JDK, and then click Next. ( e th a d ñe to us a t as nse C z lice e u sq rable á V fe e s p i l n e a r F n-t no 7. 8.

Click Next. Configure the Administrator username and password using the following settings: Name: weblogic Password: See OracleServiceBus12cPassword File (enter twice to confirm)



11. Enter the following settings for the Database Configuration Type: Vendor: Oracle Driver: *Oracle’s Driver (Thin) for Service connections; Version 9.0.1 and later


DBMS/Service: orcl Host Name: localhost Port: 1521 Schema Owner: PROD2_STB Schema Password: See OracleServiceBus12cPassword File Note: The Schema Owners in this table must match the value that you assigned to schema owners earlier when you ran the RCU utility. Do not leave it at the default with the DEV prefix because that is used for a different course. 12. Click the Get RCU Configuration button to test the connection. 13. After the test is successfully completed, click Next.


a

14. Click Next after the JDBC Test is complete. If there are connection errors, click the Back button to make the appropriate correction. 15. Click Next in the Component Data Sources page.



16. Select the following Advanced Configuration options:


• •

Administration Server Managed Servers, Clusters and Coherence




a


17. Configure the Administration server. •

Listen Address: localhost

•

Listen Port: 7071

•

Server Groups: Unspecified

a s a )h ฺ l c ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e u le li q s 18. Configure the rabServers using the following settings, and then click Next when Vá Managed completed. e f e s the existing osb_server1 before creating these two managed servers; ipDo notradelete l n e Caution: F simply -t rename the first server Node1, and then add the second server, Node2. n instead, o n Add a managed server: Name: Node1 Listen Address: 127.0.0.1 Listen Port: 7072 Server Groups: OSB-MGD-Servers-Combined Add a second managed server: Name: Node2 Listen Address: 127.0.0.1 Listen Port: 7073 Server Groups: OSB-MGD-Servers-Combined




19. Configure the cluster name as ServiceBusCluster and leave the other fields blank. Click Next.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( dthea rightuarrow, se and then click Next. 20. Assign servers to the clusters by using e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no

21. Keep the default settings in the Coherence Clusters screen, and then click Next. 22. Click Next in the Machine Configuration screen.



a


23. Click Create to start the Configuration.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da secluster was created. e 24. Review the final Configuration screen to ensureuthe ñ to sta window. 25. Click Finish and close the terminal e a C cens z ue le li q s Vá ferab e ip rans l e F n-t no



a

Practice 8-2: Initializing a Service Bus Cluster Overview


In this practice, you start and initialize a clustered Service Bus domain. Then you test failover of the cluster.

Tasks 1.

Start the Service Bus cluster in the ServiceBusClusterDomain_domain. a. Open a new Terminal window and navigate to the /u01/app/oracle/fmw_admin/12.1.3.0/user_projects/domains/Service BusClusterDomain_domain/bin directory. b.

Start the Administration server by executing the following command in the Terminal window: $ gnome-terminal -–title "Cluster AdminServer" –e ./startWebLogic.sh

a s a )h ฺ l c ฺ el ide t n uthe ewindow G Note: This command starts the server in a separate Terminal with @ t n You can also ez dserver. e appropriate title so you do not confuse it with the osb_domain u q s the ./startWebLogic.sh tu start it using a separate Terminal window with just a S v command. (fc e this a d beforeustarting s the managed servers. The Wait for the AdminServer to starteup ñ a o managed servers will takesa few minutes each to start up. t t c. Similarly, start the clustered Ca cmanaged nse servers by executing the following commands in e z the Terminal window. li the credentials weblogic/welcome1 at the time of server ue lEnter e boot-up.ásq ab r V e f e $ gnome-terminal -–title "Node1" –e "./startManagedWebLogic.sh s ipNode1" l n e a r F n-t gnome-terminal -–title "Node2" –e "./startManagedWebLogic.sh no$Node2" When you are prompted, enter the administrative credentials of the ServiceBusClusterDomain_domain as weblogic/ See OracleServiceBus12cPassword File.




2.

Initialize the cluster Service Bus configuration. a. Load a Service Bus project in the ServiceBusClusterDomain_domain domain. 1) Start the Service Bus Console (http://localhost:7071/servicebus) for the ServiceBusClusterDomain_domain, and log in as (See OracleServiceBus12cPassword File). 2) 3) 4)

5) 6) 3.

Create a new session. In the Resources section, click the Import Config Jar icon. In the Import Config Jar page, browse to /home/oracle/labs_SA/Practice_08, and open sbconfig.jar file. Click Next. On the Import Resources - Project JAR File page, click Import. Close the dialog box. Activate the session with the applicable comments.


a

Test the ValidateCredit Proxy Service. a. Start the Test Console for Projects > Practice_08 > Proxy_Service > ValidateCredit.




b.

In the Test Console, replace the value with 1234-1234-1234-1234 and click Execute.

You should see the following response indicating a valid card.

a s a )h ฺ l c ฺ el ide t c. Close the Test Console. n u e G @ t z n ecluster. e u 4. Test the failover capability of Service Bus in a Serviceq Bus d tu+ C keys in the Node2 as the S a. Shut down the Node2 managed server bycpressing Ctrl v (f e this Terminal window. Close the terminala window. ed Console b. Open the Fusion Middleware Control us (localhost:7071/em) to view the ñ a o t t server details. as nse C c. In the Fusion Middleware Navigation, select WebLogic z lControl ce Console Target The e i u Domain > ServiceBusClusterDomain_domain. server health is displayed and q Node2bisledown. sthat indicates á V fera e ip rans l e F n-t no




d.

Test the ValidateCredit proxy service three more times in the Service Bus Test Console using the same test as in Step 3 (use 1234-1234-1234-1234 for arg0). Do you see a valid response? Answer: Yes. Note: Sometimes if you execute this test very soon after shutting down Node2, you may see an Internal Server Error. Wait a minute and try the test again. e. Start the Node2 managed server. f. Shut down the Node1 managed server. g. Test the ValidateCard proxy service again in the Service Bus Test Console using the same test as in Step 3 (use 1234-1234-1234-1234 for arg0). Do you see a valid response? Answer: You should still see a valid response, because SB has failed over the managed servers in the cluster. h. Close the Test Console, but keep the Service Bus Console open for the next practice. Note: A real production environment would need a load balancer or other proxy. In this practice, the test console is somehow using some inbuilt load balancing to conduct the test.




a

Practice 8-3: Load Balancing Service Endpoint


Overview To provide insulation from unreliable credit card vendors, and also to provide additional capacity for increased load on credit card validation requests, Pega contracted multiple credit card payment vendors to ensure high quality of service, thus insulating customers from any disruptions of services caused by back-end service failures. The Credit Card Validation service is already virtualized by Oracle Service Bus. Pega’s IT department can make updates quickly and easily without any impact to either the customer (service consumer) or the back-end application developers (service provider). In this practice, you attach additional credit card validation service endpoints leveraging the advanced endpoint management features of SB. By leveraging multiple endpoints that provide the same Web service, Oracle Service Bus can guarantee service availability even if one endpoint is offline. Moreover SB will load balance service requests across endpoints according to a variety of algorithms. SB also dynamically adjusts message routing across multiple endpoints in the event that one or more are unavailable. SB automatically checks offline service endpoints for their availability, and adds them back into the active service endpoint pool when they are back online. The following graphic shows single endpoint access:

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e li u endpoint e l By implementingáthe management feature in Service Bus, the client can sqmultiple b of the service a r V even access thee services if one endpoints is down. e f s p i Fel n-tran no

a

In this practice, you perform the following tasks: • Reconfigure the validationForCC Business Service to have multiple endpoints. The Business Service will now load-balance across the two service providers: the original endpoint and the new service provider endpoint. Note: To optimize the machine resources in the classroom environment, the practice scenario load-balances the new service provider endpoints by using the admin server of the osb_domain. In this case, the admin server simulates the real-world servers hosting the service provider. In real-world, the service provider endpoints (for the same service Copyright © 2015, Oracle and/or its affiliates. All rights reserved.



•

provider hosted on multiple servers across different machines) can be load balanced directly by the Business Service. Test and monitor the endpoint utilization from the Service Bus monitoring console by invoking ValidateCredit Proxy Service several times from the Service Bus Test Console.

Assumptions •

To complete this practice, all the servers in the ServiceBusClusterDomain_domain domain and the admin server of the osb_domain should be running.

•

The Practice_08 project has been imported to the Service Bus environment.

Tasks 1. 2. 3.

Start the Node1 managed server. In the Service Bus Console for the ServiceBusClusterDomain_domain domain (http://localhost:7071/servicebus), create a new session. Add and load balance the credit service endpoints. a. In Resources, navigate to the Practice_08 > Business_Service folder. b. Click the validationForCC Business Service to access the configuration page.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e ip rans l e F n-t no c. d.

Create a session and click the validateForCC entry. Click the Transport tab to view the Endpoint URIs.



a


e.

Click the Add button to add a URI with the following values: Load Balancing Algorithm: round-robin Endpoint URI: http://localhost:7001/ServiceB_context-root/CCService_A_Port Click the edit button again to add a second URI. Endpoint URI: http://localhost:7001/ServiceC_context-root/CCService_A_Port

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s Vá ferab e s n f.elip Click Save. a r Fg. Activate -t the session with an appropriate description. n o n 4.

Test the service endpoint load-balancing capability. a. Navigate to the Practice_08 > Proxy_Service folder b. Launch the Test Console for the ValidateCredit Proxy service.



a


c.

In the Test Console, replace the value with 1234-1234-1234-1234 and click Execute.

d.

You should see the following response.

s a h l) ฺ c ฺ l nte uide e @ nt G z e u tude q s cva this S f ( da use e ñ sta se to a C cen z e u le li q s á rab and run the test a few more times, and then close the Test e. ClickV the Backebutton f e s ipConsole. l n e a r F n-t nothe service monitoring statistics. 5. View a.

In the Fusion Middleware Control Console, right-click SOA > servicebus(AdminServer) and navigate to Home > Service Health.



a


a s a )h ฺ l c b. Click Search. ฺ el ide t n u e G @ t ez den u q s tu a S v (fc e this a ed o us ñ a st se t a C cen z e c. Select the validationForCC u le li Business Service to view the aggregate service metrics. q s b the metrics page and get familiar with the available data. Take a á V minutefetorabrowse e ip rans l e F n-t no Note: Sometimes it can take a few minutes after starting one of the nodes for metrics collection. If you do not see any metrics on this page, wait for a bit longer and try again.




d.

6.

Scroll to the bottom of the console to view Endpoint URIs. Notice that the service requests are distributed across the three endpoints. Note: If you do not see any statistics or many of the columns show 0, refresh the page until they appear.

e. Log out of the SB Console and close the window. Shut down the Administration server and both managed servers in the ServiceBusClusterDomain_domain to release system memory.




a

Practice Solutions


Overview If you do not have time to complete the practices, follow the instructions below to work with the ServiceBusClusterDomain domain using all of the necessary configurations to test load balancing and failover. You must complete Practice 8-1, creating the ServiceBusClusterDomain_domain before you can complete the following Solution instructions.

Tasks 1.

Import the project file. a. Start the servers by completing Practice 8-2, Task 1. b. Start Service Bus Console for the ServiceBusClusterDomain using http://localhost:7071/servicebus (See OracleServiceBus12cPassword File). c. d.

Create a new session. Import the configuration file /home/oracle/labs_SA/Practice_08/Solutions/solution_8_sbconfig.j ar.

a s a )h ฺ l c ฺ el ide t e. Activate the session. n u e G @ 2. Test load balancing and failover. t ez dtheenfailover capability of u a. Follow the instructions in Tasks 3 and 4 of Practice 8-2 to test q s tu a S Service Bus in a Service Bus cluster. v fc this b. Start the Node1 managed server. a ( d se 8-3 to test the service endpoint e c. Follow the instructions in Tasks 4 and 5 ofu Practice ñ a e to load-balancing capability.st a s both managed servers in the C server nand 3. Shut down the Administration e z c ue le li ServiceBusClusterDomain_domain to release system memory before continuing with q s b á the next practice. V fera e ip rans l e F n-t no







a

Oracle Service Bus 12c - Administration Ed 1 (Activity Guide)

Recommend Documents