OSB-12c : Message Type Usecase

-
Apart from WSDL type’s services, we can create proxy and business service based on MessageType in oracle Service Bus.
Below are the Message Types supported in OSB

Business Service: Request: Binary, MFL, Text, XML
                                Response: Binary, MFL, Text, XML
                                           
Proxy Service: Request: Binary, MFL, Text, XML
                           Response: Binary, MFL, Text,XML

Create new folder and name it as “Messaging_Based_Service_UseCase”


Create sub folders as shown below

Create a Http based proxy service and name it as “Messaging_Based_ServiceTypePipeline”

Select service type as “Messaging” 
Note: Here in this for testing we have considered only ‘Text’ message type as remaining message types are covered earlier in MessageType section.
Request: text
Response: text


Add an ‘IF’ condition in pipeline with below logic.
($inbound/ctx:transport/ctx:request/tp:headers/tp:user-header[@name="Content-Type"]/@value)="text/plain"

In above logic we are checking content-type in $inbound, if content-type is equal to text/plain, we are considering this as success case. Else, error is raised.


If ‘IF’ condition passes, invoke ‘Messaging_MockService’ to get static valid response. Save the result content from Mock response into a variable called $response.


In Response action of Service callout, add a replace node to populate response from Mock service.


If ‘IF’ condition fails, Raise error with proper error code and description as below.
Error Code: 1001
Error Desc: Message Type Use case failed.

As mentioned above we have created a Mock service to get static response.

Here in pipeline we have included a replace activity to change body into below message.

“Message Type Use Case tested successfully.”

Deploy service into standalone local server. Once deployment is successful we can locate service in sb console.

Run Message_Based_ServiceTypePipeline 


Pass some valid text message in Request structure.


On Successful execution we will able to see response as 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