OSB 12c : Create & Configure Work Manager, Max, Min Thread Constraints

Firstly a little bit of theory. Its important you understand the concept of WM (and its as per Oracle documentation).

WebLogic Server uses a self-tuning thread pool for executing all application-related work. The pool size is managed by an increment manger which adds or removes threads to the pool when it deems it necessary.

The number of active threads will never exceed 400. 

As requests enter the server, a scheduler manages the order in which the requests are executed. When the number of requests exceeds the number of available threads, they are queued and then executed as threads return to the pool and become available. 

Work Managers indicate the type of work and priority of a request to the scheduler.

The following concepts are important to consider when assigning Work Managers to services.

1. Request and response pipelines always execute in separate threads. While the request thread originates from the proxy service transport, the response thread originates from the business service transport.

2. When external services are invoked, threads can be blocking or non-blocking, depending on the pipeline action, the Quality of Service (QoS) configuration, and the transport being used.

3. When using blocking calls, a Work Manager with a minimum thread constraint must be associated with the response in order to prevent server deadlocks.

Two key properties when configuring a Work Manager are Max Thread Constraints and Min Thread Constraints.

A maximum thread constraint limits the number of concurrent threads executing a type of request by restricting the scheduler from executing more than the configured number at one time. However, the thread pool is shared among all Work Managers, so there is no guarantee the maximum number of threads will be available for processing at any given time.

A minimum thread constraint guarantees a minimum number of threads for processing. If sufficient threads are not available in the thread pool to process up to the minimum number, the scheduler uses standby threads to satisfy the minimum. Standby threads are not counted as part of the maximum number of 400 threads in the pool. When a thread is executing a request associated with a Work Manager containing a minimum thread constraint, the Work Manager first checks the queue for another request associated with the same constraint and executes it (instead of returning to the free pool). For this reason, use minimum thread constraints judiciously. Over-use can cause resource starvation of the default Work Manager, leading to unpredictable results.

The Work Manager (dispatch policy) configuration for a business service should depend on how the business service is invoked.

If a proxy service invokes the business service using a service callout, a publish action, or routing with exactly-once QoS, consider using different Work Managers for the proxy service and the business service instead of using the same for both. For the business service Work Manager, configure the Min Thread Constraint property to a small number (1-3) to guarantee an available thread.

Now after all the theoretical details we will see how we can configure work manager in OSB 12c. The concept is similar to that of 11g however the screens have changed for OSB applications.

1. Login to Admin Console : http://host:port/console

2. Click on Lock & Edit

3. Navigate to Environments > Work Managers

4. Create New

5. Select Maximum/Minimum Thread Constraint (which ever you want to create)

6. Provide Logical Name and Count - say MaxThread4 and 4

7. Click on Next 

8. Choose the target server

9. Finish

Now again click on New 

1. Select Work Manager

2. Provide a Logical Name

3. Click Next

4. For Max and Min Threads Constraint from the drop-down select the ones you have created above

5. Finish and your WM is created with the constraints

Now assigning the WM to your service

1. Login to Service Bus console

2. Create Session

3. Navigate to your Proxy or Business Service

4. Under Transport Details Tab > from drop-down select your WM you have created.

5. Save and then Activate your session 

Helpful? Comment

Happy Learning!

Oracle ICS : Create a REST connection

Below are the steps to create REST connection in Oracle ICS to create a REST service or to call a REST service.

1. Login to ICS Console
2. On Home page, click on 'Create Connection'

3. Click on create on upper-right corner

4. Search for REST and select

5. Enter the name - Test_REST_Conn

6.
a. Select Trigger and Invoke if you are going to call another REST URL
b. If you want create a REST integration/service using this connection then only select Trigger option (connection properties will be required to be entered)

Click on create.

7. If using option a, follow below steps or go to step 12

8. Click on 'Configure Connectivity'

9.
a. Select Connection Type: REST API Base URL
b. Connection URL: Enter/Paste the REST service URL

10. If the REST API requires authentication, ex: basic authentication, then click on the 'Configure Security'

11. Select Policy: Basic Authentication, and enter the username and password and click on OK

12. Click Save and Test your connection from the upper-right corner. If the test is successful, the connection status will be 100% and ready to use.


Helpful?? Please Comment

Happy Learning!!

Oracle ICS : Create SOAP connection using WSDL URL

If you are new to ICS and want to create a SOAP WSDL connection, follow the below steps:

1. Login to your Oracle Integration Cloud domain.

2. On the Home page click on 'Create Connections' green box

3. On the 'Connections' page, right-hand corner click on 'Create'

4. On the 'Select Adapter' pop-up, search for SOAP adapter and click on 'Select'

5. You will be directed to the 'Create New Connection' dialog. Fill as below:

  a. Name - Enter a unique name for your connection (Not more than 50 char).
  b. Identifier - (No need to enter) It will be added as you key in the connection name.
  c. Role - Leave default -Trigger & Invoke
  d. Description - Enter a short description if required.

6. Click on Create.

7. A connection is created (with status at 8%). Now we will configure it (to 100%).

8. (Optional) If you to receive notifications when there a change/issue with this connection, you can enter the email address in the 'Email Address' box.

9. Click on 'Configure Connectivity' button on the right side.

10. On the Properties dialog box enter/paste the web-service WSDL URL that you want to invoke.
(Upload is when you are using a abstract WSDL to create your own service)

If the web-service WSDL requires the additional properties mentioned, select the ones necessary.

11. Click on OK
12. Scroll down of the page and click on 'Configure Security'
13. Select the type of security policy* that is required for the service and enter the values as required.

By default, the security is set to 'Username Password Token' type.

  a. Basic Authentication: When service requires username/password only to be called.
  b. Username Password Token: When the service requires username/password as WSS token
  c. No Security
  d. SAML

*You can check the security policy by loading the WSDL in the browser.

14. Done, now Save and then Test your connection.

You can either
  a. Validate and Test (Validates your entire WSDL), or
  b. Test (Syntax validation)

15. Close
16. Your connection is created and configured 100%. It will have a ✅

Done.


Helpful?? Please Comment.

Happy Learning!!