This chapter provides overview information about Service-Oriented Architecture (SOA) extensibility for Oracle Communications Network Integrity.
This chapter contains the following sections:
SOA extensibility topics covered in this chapter include creating an SOA development environment, setup, development, and testing of the Network Integrity SOA application.
The Business Process Execution Language (BPEL) provides enterprises with an industry standard for business-process orchestration and execution. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow.
The Oracle BPEL Process Manager is a tool for designing and running business processes. This product creates, deploys, and manages cross-application business processes with both automated and human workflow steps in a service-oriented architecture.
The Sample Network Integrity SOA application provides a BPEL process that contains two parallel sequences. These sequences automate search and update Network Integrity discrepancies.
The following shows how this automation occurs:
Search for Network Integrity discrepancies of type attribute mismatch for nativeEmsServiceState and update their resolution to Correct in UIM, if those discrepancies' network value is In service and import value is Out of service.
Search for Network Integrity discrepancies of type attribute mismatch for physicalAddress and update their priority to High and discrepancy owner to given input value.
The tasks involve setting up of developer environment to update and extend the Network Integrity SOA application for future requirements.
Required software includes:
Oracle WebLogic Server
Oracle JDeveloper
Oracle Application Development Framework
Oracle Application Runtime Framework
Oracle Fusion Middleware Repository Creation Utility
SOA suite
Oracle Database
To implement SOA extensibility, use the following tasks:
To install Oracle Weblogic Server, use the following procedure:
Download Oracle WebLogic Server.
Run ./wls1036_linux32.bin
Click Next.
Enter the WL_Home directory location to create a home directory for Oracle Fusion Middleware.
Click Next.
Select the I wish to receive security updates via Oracle Support check box and click Next. (Optional)
Select Custom for the installation type.
Click Next.
Select the WebLogic Server check box to install all WebLogic Server components.
Click Next.
Select the Sun JDK check box.
Click Next.
Review the installation directories.
Click Next.
Review the installation summary of the products and JDKs to be installed.
Click Next. This step begins the installation.
When the installation is complete, deselect Run Quickstart.
Click Done.
Setup BEA_HOME, JAVA_HOME, WL_HOME environment variables and update PATH with the Java executable location. For example,
export BEAHOME=/opt/beahome export WL_HOME=$BEAHOME/wlserver_10.3 export JAVA_HOME=$BEAHOME/jdk160_33_R27.6.5-32 export PATH=$JAVA_HOME/bin:$PATH
To install Oracle JDeveloper, use the following procedure:
Download Oracle JDeveloper (Oracle_JDeveloper_11g_and_Oracle_Application_Development_Framework_11g.zip) software from the Oracle software delivery website:
Unzip the installer to any directory.
Open a console.
Change the console directory to the unzipped installer directory.
Run the installer using the following command:
java –jar jdevstudio11116install.jar
The Installer starts extracting the setup files and Installation wizard opens when it reaches to 100%.
Click Next.
Select Use the existing Middleware Home to select the Middleware home you created in "Installing Oracle Weblogic Server".
Select JDeveloper Studio and ADF too install all JDeveloper Studio and ADF components.
Click Next.
Select the existing Sun SDK.
Click Next.
Confirm JDeveloper and WLS home directories and click Next.
Review the Installation summary and click Next. This step begins the installation.
Click Done when the installation is complete.
To install Oracle Application Runtime, use the following procedure:
Download Oracle Application Development Runtime software from the Oracle software delivery website:
Unzip the installer to any directory.
Open a console.
Change the console directory to the unzipped installer directory.
Run the installer using the following command:
. Disk1/runInstaller
Enter the JAVA HOME location to launch installation wizard.
Click Next.
Click Next button after Prerequisite Checks are complete.
Tip:
Install the required system package if a check fails.Click Browse and navigate to WL_Home.
Click Next.
Click Install.
Click Next after the installation is complete.
Click Finish.
To install Oracle SOA Suite, use the following procedure:
Download Oracle SOA Suite software from the Oracle software delivery website:
Unzip the installer to any directory.
Open the console and change to unzipped folder directory.
Run the installer using the following command:
. Disk1/runInstaller
Enter the JAVA HOME location to launch installation wizard.
Click Next.
Click Next after Prerequisite Checks are complete.
Tip:
Install the required system package if a check fails.Click Browse and navigate to WL_Home. Do not modify the Oracle Home Directory name.
Click Next.
Click Install.
Click Next after the installation is complete.
Click Finish.
To creates a metadate service (MDS) schema for the Business Activity Monitoring (BAM) and SOA servers, use the following procedure:
Download Oracle Fusion Middleware Repository Creation Utility software from the Oracle software delivery website:
Unzip the Repository Creation Utility (RCU) to any directory.
Open the console and change to unzipped folder directory.
Run the installer using the following command:
./rcuHome/bin/rcu
Click Next.
Select Create in the Create Repository screen
Click Next.
Enter database details as required.
Click Next.
Click OK.
Select Create a new Prefix in the Select Components screen and enter a prefix in the text box.
Select the following from the Component list:
Metadata Service
SOA Infrastructure
Business Activity Monitoring
User Messaging Service
These components are required for the SOA and BAM servers.
Tip:
Remember the Schema Owners for subsequent procedures.Click Next.
Enter passwords for all components in the Schema Passwords screen.
Tip:
Remember the Schema Passwords for subsequent procedures.Click Next.
Review the Schema Owner, Tablespace Type, and Tablespace Name for each Component in the Summary screen.
Click Next to accept the settings.
Click OK to create the tablespaces.
Click OK when the prerequisites are complete.
Click Create in the Summary screen to create the tablespaces. This step can take up to ten minutes.
Click Close after the tablespaces are created.
SOA design time in JDeveloper requires a JDeveloper extension called SOA Composite editor. While this is normally updated over the network when using release-level software, you can also perform the update manually if you have the extension file. JDeveloper periodically prompts you to accept an automatic network update. Since this is released software, you have the option to click OK to update to a newer version.
To update JDeveloper for the latest SOA Composite editor, use the following procedure:
Start JDeveloper Studio.
Select Default Role.
Deselect Show this dialog every time.
Click OK.
Click No for Migrate from previous release. After starting JDeveloper, wait for the Integrated Weblogic Domain to be created. This domain is created the first time you run JDeveloper after installation. It is not used by SOA. Watch for the completion message for setting up the domain in the JDeveloper Messages log window at the bottom of the JDeveloper IDE:
[12:37:11 PM] Creating Integrated Weblogic domain... [12:38:05 PM] Extending Integrated Weblogic domain... [12:38:14 PM] Integrated Weblogic domain processing completed successfully.
Now you can update the SOA Composite editor extension. These instructions show you how to update the extension over the network.
Select Help | Check For Updates.
Click Next.
Select Search Update Centers.
Select Oracle Fusion Middleware Products.
Click Next. The system searches the update center for extensions.
From the list of extensions, select Oracle SOA Composite Editor.
Click Next to begin downloading. When the extension finishes downloading, it is listed with the version number detail.
Click Finish.
Restart JDeveloper when prompted.
Click No for Migrate from previous release.
When JDeveloper is running again, select Help then About.
Select the Version tab and review the version.
To creates an Oracle WebLogic domain with the required products for SOA applications, use the following procedure:
Open the console and change to unzipped folder directory.
Run the following command:
./<BEAHOME>/wlserver_10.3/common/bin/config.sh
When the Welcome screen appears, select Create a new WebLogic domain.
Click Next.
Select Generate a domain, SOA Suite, Enterprise Manager, and Business Activity Monitoring. Dependent products are selected automatically.
Click Next.
Enter domain1 for the domain name.
Click Next.
Enter the user name weblogic and a password. The password welcome1 is assumed in this document.
Click Next.
Select Sun SDK 1.6_33 and leave Development Mode checked.
Click Next.
Select the check boxes for the components that you want to change.
Enter Welcome1 for the Schema Password.
Change the Service, Host Name, and Port values as required.
Click Next.
Review the Schema Owners for the individual component schemas and confirm that the owners match those selected in the "Creating SOA Metadata Service Schemas" procedure.
Tip:
To change the Schema Owner field, use the following steps:Remove the check boxes for all Component Schema items.
Select the check box for the Component Schema that you want to change.
Change the Schema Owner field.
Remove the check box for the component schema item you changed.
Click Next to begin a data source connection test.
Click Next if all connection tests are successful. If the connection tests are not successful, click Previous and correct any errors.
Click Next.
Click Create in the Configuration Summary screen.
Click Done when the domain has been created.
When a domain is created, the Configuration Wizard creates one admin server and two managed servers with the following details:
Admin Server
Name: admin_server
Port: 7001
SOA Server
Name: soa_server1
Port: 8001
BAM Server
Name: bam_server1
Port: 9001
See the startManagedServer_readme.txt file in the domain folder to start the servers.
To update an SOA application using the Network Integrity SOA application, use the following procedure:
Download the Sample Network Integrity SOA application (NetworkIntegrity-SOA_Sample_App-version.zip) software from the Oracle software delivery website:
Unzip the application to any directory.
Start Oracle Jdeveloper.
From the Jdeveloper main menu, choose File then Open then browse to NISOAApplication folder and select NISOAApplication.jws.
Click Open.
The NISOAApplication.jws contains the NIDiscrepancyService project. The main components for this project are:
NetworkIntegrityControlService.wsdl: This is the Network Integrity Sample Web Services WSDL file.
xds: This folder contains Network Integrity Sample Web Service schema files.
composite.xml: This file describes the entire composite assembly of services, service components, references, and wires
In the project, composite.xml file is automatically created when the SOA project was created. In this application only service components (including Network Integrity Sample Web Service) are used.
NIBPELDiscrepancyProcess.bhel: This file contains a list of variables and the main sequences in which he Network Integrity Web Service calls to update the Network Integrity Discrepancies are defined. There are two parallel sequences named as Sequence_1 and Sequence_2 to update Attribute mismatch discrepancies for nativeEMSServiceState (go to step 6) and physicalAddress (go to step 8) respectively.
It is necessary that both client side artifacts (wsdl and schema) and server side artifacts are in sync and of same version.
To search for natieEMSServiceState attribute mismatch discrepancies (Sequence_1), search for the following discrepancies:
TYPE = ATTRIBUTE_VALUE_MISMATCH
ATTRIBUTEORRELATIONSHIPNAME = nativeEmsServiceState
STATUS = DISCREPANCY_OPENED
COMPARESOURCE = INVENTORY
REFERENCESOURCE = NETWORK using findDiscrepancy webservice operation.
Loop over each discrepancy and submit to updateDiscrepancy if COMPAREVALUE = 'IN_SERVICE' and REFERENCEVALUE ='OUT_OF_SERVICE' to update OPERATION as 'Correct in UIM' and STATUS as 'OPERATION_IDENTIFIED'.
To search for physicalAddress attribute mismatch discrepancies, search for the following discrepancies:
TYPE = ATTRIBUTE_VALUE_MISMATCH
ATTRIBUTEORRELATIONSHIPNAME = physicalAddress
STATUS = DISCREPANCY_OPENED using findDiscrepancy webservice operation.
Loop over each discrepancy and submit to updateDiscrepancy by setting PRIORITY to High and DISCREPANCYOWNER to given value.
Right-click composite.xml and select Configure WS Policies to add appropriate security client policy to the Network Integrity Web Service component.
Update NetworkIntegrityControlService.wsdl's SOAP address location with Network Integrity Web Service URL. For example:
<soap:address location="https://<host_address>:<ssl_port>/NetworkIntegrityApp-NetworkIntegrityControlWebService-context-root/NetworkIntegrityControlServicePortType"/>
This should be done before building the SOA application or use deployment plan while deploying the SOA application to update the SOAP address location with the Network Integrity Web Service URL. This configuration is required for SOA application to communicate with Network Integrity Web Services.
To start and stop SOA servers, use the following procedure:
To start the Administration Server run to following command: <domain>/startWeblogic.sh
To start the SOA managed server, run the following command (here soa_server1 is name of SOA managed server): <domain>/bin/startManagedServer.sh soa_server1
To enter the WebLogic console, use:
http://Host_Address:7001/console
To enter the Enterprise Manager console, use:
http://Host_Address:7001/em
To enter SOA Infra, use:
http://Host_Address:8001/soa-infra
Press Ctrl + C to stop the servers.
To build and deploy the SOA application, use the following procedure:
In Jdeveloper, go to Application Navigator then right-click NIDiscrepancyService project.
Click Make NIDiscrepancyService.jpr in the menu to build the project. The project should build successfully without any compilation errors or warnings.
Start the Administration and SOA servers that are created as part SOA domain creation (see "Starting and Stopping SOA Servers" and "Creating WebLogic Domain with SOA Products").
Create a standalone server connection for the SOA server.
Right-click NIDiscrepancyService and select 'Deploy' to Application server.
The SOA suite provides an ant script to deploy and undeploy the SOA archive (SAR) file (deployable SOA application jar) in the BEA HOME. Use the following to deploy and undeploy the SAR file:
To deploy, use the following:
ant -f <BEAHOME>/Oracle_SOA1/bin/ant-sca-deploy.xml -DserverURL=<http://soa_server_host:soa_server_port> -DsarLocation=<SOA archive file path>
For example,
ant -f /home/beahome/Oracle_SOA1/bin/ant-sca-deploy.xml -DserverURL=http://<localhost>:8001 -DsarLocation=/home/example/beahome/mywork/NISOAApplication/NIDiscrepancyService/deploy/sca_NIDiscrepancyComposite_rev1.0.jar
To undeploy, use the following:
ant -f <BEAHOME>/Oracle_SOA1/bin/ant-sca-deploy.xml undeploy -DserverURL= <http://soa_server_host:soa_server_port> -DcompositeName=<SOA composite name> -Drevision=<SOA composite version>
For example,
ant -f /home/beahome/Oracle_SOA1/bin/ant-sca-deploy.xml undeploy -DserverURL=http://<localhost>:8001 -DcompositeName=NIDiscrepancyComposite -Drevision=1.0
To test a sample SOA application, use the following three tools:
Note:
Oracle Enterprise Manager (EM) can also helpful in debugging and auditing of BPEL sequence exceptions.To test a sample SOA application with EM, use the following procedure:
Log on to the Enterprise manager as admin.
Expand the SOA folder to the deployed composite (NIDiscrepancyComposite).
Click Test to test composite.
Enter any value for the input argument for SOA Web Service.
Click Test Webservice. Wait for a response.
Click Launch Message Flow Trace to see detailed output.
Click NIBPELDiscrepancyProcess to view the Audit Trail, Flow, and so on.
Expand the payloads to see detailed input and output of each Web Service invoked.
To test a sample SOA application with soa-infra, use the following procedure:
Log on to soa-infra using the following URL:
http://Host_Address:8001/soa-infra
Enter any input required for the test.
Click Invoke.
To test a sample SOA application with the Simple Object Access Protocol (SOAP) UI tool, use the following procedure:
Create a SOAP UI project at the following URL:
http://Host_Address:8001/soa-infra/services/default/NIDiscrepancyComposite/nibpeldiscrepancyprocess_client_ep?WSDL
Enter any input required for the test.
Create a request run.