Connection Pool Closed

Connection Pool Closed

If You found following error in Admin Server Log

 

Solution

Increase Max Connection parameter for reported "Data Source(EbsAppsDS)"and bounce admin server

Configure SOA Suite 11g for sending email notifications

One of the ways of the SOA Suite 11g for communicating with the outside world – apart of course from web service calls and interaction via technology adapters – is through the new User Messaging Service (UMS), a facility installed in the SOA Domain during installation of the SOA Suite. The UMS enables two-way communication between users (real people) and deployed applications. The communication can be via various channels, including Email, Instant Messaging (IM or Chat), SMS and Voice. UMS is used from several components in Fusion Middleware, for example BPEL, Human Workflow, BAM and WebCenter and can also be used from custom developed applications.

Prerequisites

Before you can apply this article, you need to have installed the SOA Suite 11g, configured the SOA Domain and have the AdminServer and the SOA Server running. You also need access to the Oracle Enterprise Manager Fusion Middleware Control Console.

Step 1: Configure the UMS Email Driver

The User Messaging Service comes with a number of drivers that each handle traffic for a specific channel. One of the drivers controls the email channel. This driver needs to be configured with the properties of the Mail Server and the email account from which emails are sent.

Go to the Oracle Enterprise Manager Fusion Middleware Control Console (typically http://hostname:8100/em) and open the User Messaging Service node. From the drop down menu in the right hand pane, select the option Email Driver Properties:

The properties that need to be configured for sending emails are indicated in the red rectangle. They are:

·         OutgoingMailServer –  (Get in touch with the messaging team in your organization)

·         OutgoingMailServerPort – (Get in touch with the messaging team in your organization)

·         OutgoingMailServerSecurity – (Get in touch with the messaging team in your organization)

·         OutgoingDefaultFromAddress – stgsoa3@inetmail.emrsn.net (stgsoa3 is my instance name. you can put any thing you like.)

·         OutgoingUsername –  (Get in touch with the messaging team in your organization)

·         OutgoingPassword –  (Get in touch with the messaging team in your organization)

Press Apply.

 Step 2: Configure the SOA Suite Workflow Notification properties

To make sure that (email) notifications are really sent to the email server, we also need to adjust a setting for the SOA Suite Workflow Notification. Navigate to the properties form via the dropdown menu for SOA Infrastructure, under SOA Administration:

The Workflow Notification Properties are shown. Only one is really important at this point: the Notification Mode (default value is None) must be set to either All or Email, otherwise any notification is not really sent onwards by the SOA Suite to UMS!

Click on Apply

Now restart the SOA Managed Server. If you don’t restart the managed server the email notification doesn’t work!

Ask developers to test if sending emails works.