12c SOA - XA DataSource creation in Weblogic console

Implementation steps:

Services⇾Data Sources⇾New⇾Generic Data Source

Provide data source Name, JNDI name

Choose Database Drive. XA and Instances connections.

Next

Provide DB connection deatils Host,port, User name and password and DataBase name i.e, Sid/service name.

Test Connection

Once Connection is success. Next

Choose target manage servers

Activate changes

Open the created data source ⇾ Monitoring tab and test the data source choosing the manage servers.

12c SOA -DB Adapter singleton property in High Availability Environment

Problem Description:

There was a problem which one can face in high availability environment (clustered) . The clustered nodes are start polling the data in Parallel mode which leads to poll the same data by all the nodes. Here it is 2 nodes clustered system. so it polls 2 copies of the same data(2 instances with same flow ids).

Solution:

We need to use singleton property in our pooling component / DB Adapter. To enable this feature for high availability environment for a given inbound adapter endpoint, one must add the singleton JCA service binding property in the composite.xml within the <binding.jca> element and set it to a value of true.

Singleton Property in composite.xml

    <binding.jca config="bindin_file.jca">

        <property name="singleton">true</property>

    </binding.jca> 

Now we can see it's polling only one copy of the data.

 

OSB - Pipeline Alerts

Here we will see how to create pipeline alerts and then locate pipeline alerts produced in 12c Service Bus run time environments in EM console.

Create a new Alert Destination – to later on send the alerts to:

Set the name for Alert Destination then press Finish:

Configure the Alert Destination – ensure that Alert Logging is on. If needed, here we can configure Email or JMS here.

Open the Pipeline editor. Add an Alert activity to the Request pipeline:

Configure the Alert activity as shown here:

The next step is to run the pipeline or the proxy service. 

In the Enterprise Manager FMW Control, the Pipelines Alerts can be inspected in the home page for the Service Bus node (that takes the place of the Operations tab). The first tab provides an overview of various types of (recent and aggregate) information.

The second tab provides details on recent as well as not so recent Alerts. On this tab can selected alerts also be purged.

When you click on the alert summary link, a pop up appears with the alert details:

On the home page for the Service Bus Project can we check the services in the project.

We can  switch to the Operations tab get a more detailed overview per operation of what operational settings have been made. On this page, the pipeline needs to have Pipeline Alerts enabled in order for pipeline alerts to be produced from it:

If we enable monitoring, the Service Bus will start to collect aggregate information about the number of messages, errors, alerts etc. This information can be reviewed on the Dashboard tab for the Pipeline:

12c OSB - Enabling Logging

Here we will see how to add log activity and enable logging settings in EM console.

Topics covered:

• Enable logging in Global Settings
• Enable logging at Pipeline level
• Add log activity to pipeline
• Message or execution tracing

Enable logging in Global Settings:

Login to EM Console and navigate to SOA⇾service-bus (Admin Server).

Click on Global Settings tab and set Logging Enabled property. We can also enable Monitoring, Alerts, Reporting and Result Cache as shown below.

Pipeline Settings

In EM Console, navigate to SOA⇾service-bus ⇾<<Service Bus Project>>. Go to Operations tab and query for Pipelines. Here we can see all monitoring related properties for Pipelines

Click on Pipeline and go to Properties tab to enable Logging as shown below. We can set other Monitoring and Tracing related properties as well. We can also set log level so that it will be shown in log files.

Add log activity in pipeline

Test 

This logging information is shown in <<osbservername>>-diagnostic.log.

Message or execution Tracing:

Message or execution tracing in Service bus (SB) allows insight into the message exchange between Service bus and it’s communication partners (Client applications and Service providers) as well as the message processing within  a pipeline. Information about incoming and outgoing messages, the corresponding headers, the course of variable manipulations and other things are written to the diagnostic logs and can be inspected there, when the tracing is active. By default the message and execution tracing are disabled, due to performance reasons and so it should only be enabled in development environments for debugging purposes.

Enablement of message tracing for proxy or business service or execution tracing on the pipeline level, can be done using Fusion Middle-ware Control (Enterprise Manager).Under a specific SB project, the corresponding services and pipelines can be found. Enabling the tracing can be simply done by checking the options for message tracing respectively execution tracing in the Operations tab.

Afterwards it should be checked, if the Log configuration on SB level is set to Notification at least. The default configuration for a Default Domain is Warning, which means that no logs are written to the diagnostics logs, even if the configuration on the component level is defined as described before. 

Outlook Web - how to edit or delete rules

To create a rule in Outllok Web Access.

Click New Rule ⇾Click the desired option to select it.

To edit a rule in OWA.

1. Select the rule from the rules window by clicking it.

2. Click Change Rule to open the rule editing window.

3. Make the changes that you want.

4. Click Save to save your changes.

To delete a rule in Outlook Web Access.

1. Select the rule from the rules window by clicking it.

2. Click Delete.

3. A window will pop up asking if you want to permanently delete the selected items.

4. Click OK on the confirmation window to permanently delete the rule.

Outlook Web Access acts on rules from top to bottom in the order that they appear in the Rules window. To change the order of rules, click the rule you want to move and then click the up or down arrow to move the rule to the position that you want in the list.

You can also add an option to a rule to stop processing additional rules against any message that the rule applies to. This is useful if a message comes in that meets the criteria for more than one rule, but you want only one of the rules to be applied.

Edit /Delete steps:

12c OSB - Message reporting

Here we will see how to use report and track from em console.

Steps:

Open the pipeline and drag and drop Report into a stage.

Provide the Content, Key name, variable as body and xpath for the key.

Deploy the code and test.

Open EM console and SOA⇾Service-bus

Service Bus ⇾ Message Reports

Search

You can see CountryName=India  report column. click here and you will get the body messages and other details.

12c OSB - Alert vs Log vs Report

We have 3 out-of-box options for reporting in OSB, below are the differences between them. We can choose one of them based on our requirement.

Log:

• One of the basics way of logging in the Oracle Service Bus is adding Log Action in every corner of your proxy service.
• When really debugging a service it’s usually a matter of “what goes in” and “what goes out” and where did my transformation go wrong. So instead of flooding your services with Log Actions, OSB gives an alternate option of enabling Execution tracing(You can find it on each service on the Operational Settings tab, called execution and message tracing).
• Once we enable the Execution Tracing, the log file will show the full content of MessageContextImpl in every step (stage, route, etc) of the service. The MessageContextImpl holds are the variables like $body, $operation, $inbound and $header you need. – Only Problem in this option is we will end up in logging everything in the server. – Extremely easy to configure but little difficult to track the message in server logs.- Performance impact will be there since all the data is written into one single log file.

Please visit this for the logging implementation steps 12c-osb-enabling-logging.

Alert:

• An alert action in a pipeline is configured to raise alerts when such predefined conditions are encountered.
• You can also configure email and JMS alert destinations to receive a notification of the alert, and send the details to the alert recipient in the form of payload.
• Pipeline alerting can also be used to detect errors in a message flow.

Please visit this for alert implementation steps osb-pipeline-alerts.

Report:

• Reports mainly used for Track/Monitor the inbound and outbound messages in the proxy services.
• We can add a Report action in our Request-Response pipeline of our service.
• The expression field holds the part we actually want to trace – Usually the $Body or Specific Content of the Body element.
• The Key Name is best used for your reference and let you easily search later on. Which is identical throughout all service calls in the business process. – Correlation Id or Specific element from the body which we can use for tracking during production.

Click here to know steps for Message reporting 12c-osb-message-reporting