Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 6

Apply Pipeline Template to service:

To apply pipeline template to service implement the following steps:

1. Login into OWSM as admin/oracle
2. Click on Policy Management -> Manage Policies This brings with list of gateways registered.
3. Click on Policies link against gateway , this brings all services registered under gateway
4. To edit the policies, click on Edit icon for the service you want to apply policies/pipeline templates.
5. To apply request pipeline template (TestServiceEncryption) we created in our previous blog, click on Replace Pipeline against request.
6. Select the TestServiceEncryption pipeline template from the list and click on select button.
7. Click the Replace button to apply the request template.
8. Click the Next -> and the Save button and then commit the policies.

Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 5

Create Pipeline Template for Verify signature on all incoming (Request) messages:

Pipeline templates are reusable policy pipelines and give consistency across the services to apply policies. To create a pipeline template follow the steps below:

1. From the Web Services Manager Control navigation pane, select Policy Management -> Pipeline Templates.

2. Click Add New Pipeline Template to add new pipeline template.

3. Select the type of component. Let’s choose Gateway

4. Select Pipeline Type from list. Let’s Choose: Request

5. Enter the name for Pipeline Template Name field. Let say: TestServiceEncryption

6. Click Next.

Now you can configure policy steps for pipeline. If you want to verify the signature of the service you can achieve with following steps:

1. Log: to log the message with encryption key, if you require to log incoming message or you like to see logs for any other purpose. its completely optional step.
2. Verify Signature : To verify the signature of incoming message

Click on ‘Add step below’ link and to create policy steps on template. Add above steps Log, Verify Signature by clicking ‘Add step below’ link twice and choose the step accordingly.

Once you done with above steps you need to configure each step individually.

1. You can leave Log policy step with default values, to log entire message.
2. Verify signature configuration need following details to enter:

Keystore location: Location/path of key store (explained in my earlier blog to cerate new digital certificate).

Verifying Key store Type: Choose jks from the list. Default to jks.

Key store password: password of key store while creation.

Signer’s Public-key alias: alias name of the key store specified while creation.

Remove Signatures: set true to remove the digital signature after verification.

Enforce Signing:  set to true, so that all incoming requests are signed.

Once done with filling details above press ‘Ok’ button.

For more details please look into Oracle Web Services Manager Administrator’s Guide on following URL:

http://download.oracle.com/docs/cd/E12524_01/web.1013/e12575/toc.htm

I will explain in my next blog: how to add above created pipeline template (TestServiceEncryption) to service in a Gateway.

Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 4

Generate digital certificate using Java Key tool:

Login into SOA Server file system as oracle user.

1. Create ‘keystore’ folder if not exists under $ORACLE_HOME/owsm path
2. Now change directory to $ORACLE_HOME/owsm/keystore
3. Run following to generate digital certificate

keytool -genkey -alias seshkey -keyalg “RSA” -keystore seshkeystore -storepass  password123

seshkey, seshkeystore, password123 can be replaced with whatever values you like to

1. Once you run above command it will ask for enter the data like your first and last name …etc.
2. Once you complete with data entry it will generate the digital certificate in $ORACLE_HOME/owsm/keystore path by name seshkeystore

For more details please look into Oracle Web Services Manager Administrator’s Guide on following URL:

http://download.oracle.com/docs/cd/E12524_01/web.1013/e12575/toc.htm

Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 3

Create Services in OWSM Gateway:

Create services using OWSM to secure webservices, BPEL, ESB services.

TO add services: log in into OWSM as admin/oracle

1. click on Policy Management -> Register Services
2. Against your new gateway which you created , click on the Services link
3. To register new service to secured from gateway click on ‘Add new service’ button.
4. Enter the service details into the fields for example:

• • • Service Name – TestService
    • Version – 1.0
    • Service Description – Test service description
    • WSDL URL – http:/yourserver:port/…/?WSDL

1. press Next button
2. Check the URL field is same as WSDL URL entered in previous screen. Keep default values for other fields and click ‘Finish’ button.

You can see above registered service in list of registered services in gateway.

Commit the changes now. If changes are not committed it will not take effect.

You can test the above created service using testing tool in OWSM

Copy the above service WSDL URL:

http://soaserver:port/gateway/SID000..?WSDL

or

http://soaserver:port/gateway/TestService?WSDL

Click on Tools-> Test Page from left hand menu of OWSM

Enter the above URL into ‘Enter WSDL URL’ field and press Submit Query  button.

If test is fine then you can see user interface to enter parameter values for  Webservice.

For more details please look into Oracle Web Services Manager Administrator’s Guide on following URL:

http://download.oracle.com/docs/cd/E12524_01/web.1013/e12575/toc.htm

I will cover generating certificate using Java Keytool and use it with OWSM services in my next blog…

Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 2

Create New Gateway in OWSM:

1. Login into Webservices manager Control http://soaserver:port/ccore as admin/oracle

2. Click  on Policy Management –> Manage Policies

3. Click on Add New Component button

4. Then enter the following details

• Component Name = <gateway>_gateway (i.e. vbs_gateway)
• Component Type = Gateway
• Container Type = Oracle Web Services Manager
• Component URL = http://<soaserver>:<port>/gateway

6. Once done with all details filled then click on register button.

Once Gateway is created now you can add services to it.

You need to deploy newly created gaetway in OWSM, implement following steps to deploy :

• Get the gateway Id for newly created gateway (e.g. C0003001)
• Open the gateway-config-installer.properties file following path: $ORACLE_HOME\owsm\config\gateway\
• Change the   gateway.component.id to your new gateway component id
• gateway.component.id=C0003001
• Deploy/redeploy the gateway with following command

wsmadmin.sh deploy gateway –Doc4jAdminPassword=<password>

For more details please look into Oracle Web Services Manager Administrator’s Guide on following URL:

http://download.oracle.com/docs/cd/E12524_01/web.1013/e12575/toc.htm

Creating Services in gateway will be covered in my next blog…..

Oracle Webservices manager (OWSM), 10.1.3.4 configuration in a nutshell – 1

Configuration of OWSM to secure webservices, BPEL, ESB processes

1. Create a new gateway or use default gateway

2. Create Services in Geateway

3. Generate Digital certificate using java keytool or import existing Digital certificate.

4. Create Pipeline templates for Request/Response

5. Assign certificate or remove certificate or create logs on pipeline templates

6. Apply required (Request/Response) templates to services

I will cover above steps briefly in my next blogs….

For more details please look into Oracle Web Services Manager Administrator’s Guide on following URL:

http://download.oracle.com/docs/cd/E12524_01/web.1013/e12575/toc.htm

Human Task Form auto generation in BPEL process using JDeveloper

After you are done with adding HumnTask activity in your BPEL Process:

Let’s say you named Human Task as humanTaskErrorInfo in BPEL Process.

In JDeveloper (10.1.3.4) Application Navigator,

Right click on humanTaskErrorInfo folder (right below Integration Content folder)–> select Auto Generate Simple Task form.

Now you can see following folder structure under Web Content Folder in Application Navigator.

humantaskErrorInfo\form\ear

humantaskErrorInfo\form\war

If you would like to do simple modifications on Human task Form then you can edit payload-body.jsp, payload-body.xml files under humantaskErrorInfo\form\war path.

After deploying the BPEL process , Human interventions can be accessed from following URL http://yourSOAServer:port/integration/worklistapp

“ora:processXSLT(‘logMessage.xsl’,bpws:getVariableData(‘inputVariable’))”, the reason is FOTY0001: Type error…..

BPEL Exception in Transform activity:

Error while processing XPath expression, the expression is “ora:processXSLT(‘logMessage.xsl’, bpws:getVariableData (‘inputVariable’)) ”,  the reason is FOTY0001: Type error. Please verify the XPath query.

Solution:

Open the BPEL process project in Jdeveloper and double click on Transform activity and wait until Source part and Target Part’s are loaded and then redeploy the BPEL process to the SOA server.

If you still see the error and can’t see your latest XSLT changes then restart your SOA server or rename the XSL file name on transform activity and redeploy BPLE process

Reset/Purge ESB Cache (Slide/WebDAV)

Even after you delete ESB services from ESBControl, ESB cache will not be deleted automatically. To delete ESB cache manually you can follow the steps below:

1. Open windows explorer and click on  Add a network place and create network place for http://yoursoaserver:port/esb/slide/ESB_Projects
2. Remove the cache folder for required ESB project

BPEL process File adapter’s rejected files location in file system

Rejected files from File adapter in BPEL process can be found in following location:

$ORACLE_HOME/bpel/domains/<your domain>/jca/<your BPEL process name>/rejectedMessages/