Let’s deep dive into OSB 12.1.3 new features…
Developer productivity :
- Quick start installer for developers
You need to install Java 64 bit JDK version 1.7 or later first and then launch the fmw_188.8.131.52.0_soa_quickstart.jar.
- JDev IDE
Start creating a Service Bus Application : (File > New > Application)
- SCA like : Proxy services are no longer associated with message flow and message context. Proxy service invokes a pipeline, which is associated with its own unique message context and variables.
- Integrated OSB server on JDev :
The Weblogic Integrated Server is pre-configured with SOA Suite components runtime and JavaDB (Apache Derby). So you don’t need to run RCU.
- Testing using JDev (right click then Run)
- Continuous integration with Maven, Hudson, Jackson and Jersey
- Test XPath expressions using JDev
- Templates (template pipeline)
- Changes to template will not affect those generated pipelines whose links to the templates have been “broken”
- Ability to take a regular pipeline and save it as a pipeline template
- Ability to define locked actions in the template pipeline – i.e. those with property values that cannot be changed in the generated pipeline, e.g. annotation of a Log action
- Ability to define unlocked actions in the template pipeline – i.e. those with property values that can be changed, e.g. target service reference of the Route action
It’s a good practice to use a template to achieve Error Handling, Logging, Security…
Monitoring / Troubleshooting :
In 12c Service Bus uses ODL (Oracle Diagnostic Logging), this means that OSB logging will go to <server>-diagnostic.log instead of <server>.log. Configuration of these log files can be done via the logging.xml file. Message prefix for error messages is now « OSB ».
The OSB servers’ logging configuration is taking place in the $DOMAIN_HOME/config/fmwconfig/servers/$server_name/logging.xml
To make the OSB log action visible in the osb_server1-diagnostic.log you have to add the following line into the logging.xml file related to the corresponding osb server:
pipeline’ level=’TRACE:16′ />
- Operation setting like Monitoring, sla alerts, Message Tracing, etc, are now applicable on OEM.
- Oracle Dynamic Monitoring Service (DMS) support servicebus metrics. OSB now supports DMS Execution Context along with SOA FlowID. This will enable the admin console to display OSB proxy service, pipeline, split join component, and business service as top level components in the SOA message flow.
- OSB Instance Tracking (Jar From SOA)
- Dashboard for Alerts
- Service Health Dashboard
- Configuration of operational attributes for services
- Resequencing messages
- Message reports (view and purge)
- Security configuration
- Testing (Test Console)
- Dynamic validation
- Dynamic replace
- Shared variables :
When two pipelines in the same call chain declare a variable with the same name as shared, they will be reading and modifying the same variable.
- Concept of library XQuery library modules
Then the functions exposed by the module become available in the User defined functions: and can easily be used with the mapper:
- Enable/Disable actions and stage in a pipeline
New other features :
- Custom authentication for Business Service
- Session Stickiness fot HTTP Business Service To a specific URI entry
- nXSD Action
- Service Callout with Attachments
- New OSB Console (OSB Design)
- Throttling group resource
- MDS Support for importing and publishing shared resource
- OWSM Custom Assertions support
- Resequencer support
- ResequencerMaxGroupsLocked: Maximum number of groups locked by Resequencer in each attempt it makes to obtain locks on the groups. Locks are obtained on the groups so that only one managed server node processes the group at a time.
- ResequencerLockerThreadSleep: The number of seconds the Resequencer would pause between each iteration to obtain locks on the groups.
- DeleteMessageAfterComplete: Delete message after successful execution. The default value will be set as true.
- Full DVM and Cross References support (populate, lookup, delete via xpath functions)
- Enterprise Scheduler Service (ESS) support
- Active Adapter only started at the first request (Lazy loading)
New Adapters :
- Coherence Adapter (Put, Get, Remove, Query)
OSB Domain Topologies:
Before 12c, having a DBMS was not mandatory. It was required only if you were using the reporting feature.
Now the SOAINFRA and MDS Schemas need to be installed for the underlying components
- MDS -> OWSM (Oracle Web Services Manager) component. Policy store which requires a database for production environments as well.
- OPSS -> OPSS (Oracle Platform Security Services) Store. Which provides identity- and keystores, needs a database for a production environment as well.
- IAU -> OPSS Audit Store
- ORASDPM -> User Messaging
- SOAINFRA -> OSB Reporting Provider, Resequencer
Inbound Security is performed at the proxy service layer. As a result, inbound security related errors can no longer be handled within user-configured pipeline error handlers.
Unfortunately it is still not possible to have multiple OSB clusters in the same domain.
– Integrated Server (Java DB) -> OSB and BPEL only
– Compact Domain -> Oracle DB (Allows adding other components, such as Enterprise
Scheduler, Managed File Transfer, B2B, and Business Activity Monitoring
– Expanded Domain (what you should have in Prod)
Notions of server groups :
Following are the user extensible server groups in 12c