Components of OSB

By -

 

  1. Proxy Services: Proxy services are the entry point for client requests into the OSB. They receive messages, route them to the appropriate back-end service, and send responses back to the client.

  2. Business Services: Business services are the back-end services that are called by the proxy services. They may be web services, JMS queues or topics, FTP servers, email servers, or any other type of service that can be accessed through a transport protocol.

  3. Message Flow: The message flow is the path that messages follow through the OSB. It consists of stages, actions, and branches that define how messages are processed and routed.

  4. Service Bus Console: The Service Bus Console is the graphical user interface (GUI) that is used to configure, manage, and monitor OSB components. It provides a visual representation of the OSB and allows developers to create and modify proxy and business services, message flows, and other components.

  5. Operational Settings: The operational settings of OSB allow you to configure the runtime behavior of the OSB. This includes settings for security, transport protocols, message formats, and other runtime parameters.

In summary, the components of OSB work together to provide a powerful and flexible platform for building, deploying, and managing enterprise integrations.











In Oracle Service Bus (OSB), there are several actions that can be used to manipulate and route messages. These actions are:

  1. Assign: The Assign action is used to assign or modify message content, headers, or properties.

  2. Route: The Route action is used to route messages to specific services or endpoints based on routing rules.

  3. Service Callout: The Service Callout action is used to call another service or endpoint as part of the message processing flow.

  4. Publish: The Publish action is used to publish a message to a topic or queue on a JMS provider.

  5. Reply: The Reply action is used to send a response back to the client.

  6. Transform: The Transform action is used to transform message content from one format to another.

  7. Validate: The Validate action is used to validate message content against an XSD schema.

  8. Branch: The Branch action is used to create conditional processing paths based on message content or other criteria.

  9. Split-Join: The Split-Join action is used to split a message into multiple parts and process them separately before joining them back together.

  10. Aggregate: The Aggregate action is used to combine multiple messages into a single message.

  11. Iterate: The Iterate action is used to iterate over a repeating element in a message and perform actions on each occurrence.

  12. Error Handling: The Error Handling action is used to handle errors and exceptions that occur during message processing.

These actions can be combined and configured in a variety of ways to create complex message processing flows in OSB.

Pranay is a versatile Oracle Technical consultant. Adept in Oracle ERP development, SDLC management, design, and architecture. He has 11 years of extensive experience in Oracle Apps implementation engaged in technical development areas of Oracle Applications 11i/R12 E-Business Suite. He possesses sound knowledge in technologies like OAF, ADF, J2EE, MSCA, Oracle PaaS Cloud, Java Cloud services, ADF & XML Publisher. Currently, he is working for BirlaSoft Inc. USA. Being a Consistent solution provider in Oracle Developer Community forums earned him the title of "Technology Master”, Currently he holds 3rd position globally for providing a solution in Oracle Developer Community for the OAF Workspace. He has also authored several articles on ADF Technology, Fusion Financials, OAF & PaaS Cloud. He successfully presented the case study in Oracle Collaborate event forum on "How optimizing the Oracle Mobile App Solution Helped in Boosting the Productivity of a Warehouse."

Comments

Post a Comment

Popular posts from this blog

Sample HZ API's script to Create Contacts and Contact Points in Oracle

By -
1. Below Code will create Contact Point in Oracle . DECLARE    P_CONTACT_POINT_REC   HZ_CONTACT_POINT_V2PUB.CONTACT_POINT_REC_TYPE;    P_PHONE_REC           HZ_CONTACT_POINT_V2PUB.PHONE_REC_TYPE;    P_EDI_REC_TYPE        HZ_CONTACT_POINT_V2PUB.EDI_REC_TYPE;    P_EMAIL_REC_TYPE      HZ_CONTACT_POINT_V2PUB.EMAIL_REC_TYPE;    P_TELEX_REC_TYPE      HZ_CONTACT_POINT_V2PUB.TELEX_REC_TYPE;    P_WEB_REC_TYPE        HZ_CONTACT_POINT_V2PUB.WEB_REC_TYPE;    X_RETURN_STATUS       VARCHAR2 (1000);    X_CONTACT_POINT_ID    NUMBER;    X_MSG_COUNT           NUMBER;    X_MSG_DATA            VARCHAR2 (1000); BEGIN    P_CONTACT_POINT_REC.CONTACT_POINT_TYPE := 'EMAIL';    P_CONTACT_POINT_REC.OWN...
Read more

REST integration built-in OIC to read Large files with size more than 10MB

By -
Image
Processing large files in any integration requires a lot of effort and complex coding. Every integration platform has a limit size to read a file, similarly, the OIC service provides a limit of 10MB to read the file, if the size exceeds, then the below error will be encountered  Error Reason: Translation Error. Translation Error. Error while translating message to native format. Please make sure that the payload for the outbound interaction conforms to the schema and payload size does not exceed threshold. Error occured as File size exceeds maximum threshold size of 10 MB : Application Error Error Summary: ICS runtime execution error  In this article, we will learn how to read the big-size file in OIC.  Note only XML and CSV formats are supported for larger file read operations.  Here we will build an integration with a source FTP connector to read files containing sizes more than 10 MB  &  read them through the "Read File in Chunks" features and c...
Read more