OSB-12c : WSDL,XSDs usecase

-
Oracle Service Bus defines some types of business services and proxy services using a WSDL, an XML-based specification for describing Web services. A WSDL document describes service operations, input and output parameters, and how a client application connects to the service.

Create new service bus project and rename it as ‘ServiceType_useCase’.



 Create folder and sub folders as mentioned below.

Create new XML schema and name it as “SampleRequest.xsd”.
XSDs (Right Click)  New -> XML Schema


A pop up window will appear name XML schema as “SampleRequest.xsd”.


In below screen shot you can see design view of XML schema.
Rename Root element as “SampleRequest” and add sequence to it.
SampleRequest  (Right Click) Insert Inside Element -> Sequence




Similarly add element inside sequence.


Add two elements inside sequence and name it as ‘Input1’ and ‘Input2’.


Similarly specify datatype for elements.
(Right Click) Input1 -> set Type -> xsd: float
Note: Here we have considered data type as float, but you can choose any data type as per requirement.




Similarly create response schema and rename it as “SampleResponse.xsd”.


Specify element and name it as “Output” and set data type as “double”.


Next we need to create WSDL using these schema files.
WSDL -> (Right Click) -> New -> WSDL (Builder)




Name WSDL as “SampleTest.wsdl” and select Interface type as “Synchronous Interface.”
Binding: execute_bind
Port Type: execute_ptt
Operation: execute
Interface Type: Synchronous Interface



In ‘Input’ section of WSDL builder click on ‘+’ and select element type of “SampleRequest.xsd”. Specify part name as “Request”.





Similarly in ‘Output’ section of WSDL builder click on ‘+’ and add element type of “SampleResponse.xsd”.Finalized WSDL builder will be shown as below.



Below is design view of WSDL.


Create new http based proxy service along with pipeline.



Name pipeline service as “WSDL_Based_ServiceTypePipeline”. Select option in Template.(Click on check box)



Select RoBTESB_REQ_WSDL_CapabiltiyAccessPipeline_Template


Select Created “SampleService.wsdl”




Note: Here in this case we have created Mock service to get static response like “WSDL based service type tested successfully.”


Add a Service Callout activity and invoke created “WSDL_MockResponse” service.
Response from mock service will be saved in a variable called ‘$response’.



In Request action of Service callout add a Transport Header activity and add new header with below details.
Direction: Outbound request
Action: Set
Name: transportHeader
Value: WSDL.



In addition to Transport Header, add one assign node in request action of service callout and include logic to sum up values of input.

sum(($body/exam:SampleRequest/exam:Input1,$body/exam:SampleRequest/exam:Input2))

Save result in a variable called ‘$addedResult’.



Add a replace activity in Response action of Service callout and replace body with contents of $response (output result from Mock service).




Next add an Insert activity to insert contents of $addedResult into changed body.




Deploy service into standalone server and once deployment is successful, we can locate this service in sb console.


Run WSDL_Based_ServiceType pipeline.


Pass some valid values as shown below in request structure.



One successful execution we will get response as shown below.


Location: Bengaluru, Karnataka, India

Comments

Post a Comment

Popular posts from this blog

OSB-12C : XA Transactional Support feature

-
Image
OSB 12c supports both XA as well as Non-XA transactions. An XA transaction is a "global transaction" that may span multiple resources. It involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. XA transactions come from the X/Open group specification on distributed, global transactions. JTA includes the X/Open XA spec, in modified form. XA gets involved when you want to work with multiple resources - 2 or more databases, a database and a JMS connection, all of those plus maybe a JCA resource - all in a single transaction. In this scenario, you'll have an app server like WebSphere or Weblogic or JBoss acting as the Transaction Manager, and your various resources (Oracle, Sybase, IBM MQ JMS, SAP etc) acting as transaction resources.  Your code can then update/delete/publish/whatever across the many resources. When you say "commit", the results are committe...
Read more

Static code analysis of Terraform .tf files using ‘Checkov’ — Secure your infrastructure

-
Image
  Hands on shelf! We can all agree that Terraform is great tool for infrastructure creation and provisioning. When we write terraform .tf files for infra creation we might miss something and we add something which can lead to security issues. Security should be prime factor for any devops related use-case. When I was searching internet for is there any tool which will scan terraform files and give a picture what may go wrong (from security perspective), I came across this very useful tool named ‘Checkov’ Link :  https://www.checkov.io/1.Welcome/Quick%20Start.html Checkov is a   static code analysis tool for scanning infrastructure as code (IaC) files for misconfigurations that may lead to security or compliance problems. Checkov includes more than 750 predefined policies to check for common misconfiguration issues. In this post, I am going to discuss how to do static code analysis of terraform tf files using checkov. step 1 : Install checkov in your machine. $ pip install...
Read more

OSB12c : Schema Validation - Dynamic Validation

-
Image
We can use validate node in OSB to validate schema. There was an option to validate the payload in OSB 11g but it was static, however from 12c there is a new feature included in the OSB validation activity that is validating the data dynamically. This will allow the user to validate the input data or other data dynamically based on certain condition. Thus the process can be stopped at the beginning itself the data validation goes wrong. You have the option to save the validation result or raise an error. Use case: 1. Create a WSDL based service 2. Add validate (dynamic) to validate incoming request structure. 3. If any violation in request structure compared with schema, Error will be raised with proper error code and description. Create new folder and name it as ‘DynamicValidateSchema_UseCase’. Create sub folders structure as shown in below image. For this use case we have created two XSDs and placed it inside Resources -> XSD folder EmployeeDetailsReq...
Read more