Create schedulers in websphere.

You can create multiple schedulers within a single server, cluster, node or cell. Each configured scheduler is an independent task scheduling engine that has a unique Java Naming and Directory Interface (JNDI) name, persistent storage device and daemon.

Procedure

1. Configure schedulers.
2. Create the database for schedulers(same as our data source creation)

1) Set scheduler in WebSphere console (you'll need database connection set as well, because scheduler automaticly creates few tables for managing tasks)

Go to resources -> schedulers -> new

Set JNDI name by which you'll call Scheduler from your application (in this example, it will be sched/testScheduler), and ofcourse choose database conneciton.

Poll interval - i'm not sure what is purpose of it because i set interval for tasks in application, but anyway i set it to 30min.

Table prefix - i guess choose whatever you prefer

Now after you created new Scheduler, select it in table (resources -> schedulers) and click 'Create tables'.

Results

A scheduler is now configured and ready to use for newly installed applications. If the scheduler JNDI name is not yet visible to your application, restarting the application or restarting application server will allow the scheduler to be seen.

When schedulers are created for the first time, the poll daemon will not automatically start and must be started manually and will only start automatically the next time the server is started. To start the poll daemon manually, refer to the scheduler daemons topic.

Attention: Changes to existing scheduler configurations will not take affect until after the application server is restarted.

WebSphere portal content will share soon..

How to enable probe in DataPower

Login to DP console  >> > control panel

Click on required services -à Click on Services name

Click on Show Probe button à click on Enable probe.

Creating an XML firewall and Configuring the transform action in Data power

invoking a service endpoint exposed by DataPower from an SCA component

Here are the high-level steps to invoke a service endpoint exposed by DataPower from an SCA component:

1. Create a pass-through XML firewall service.
2. Set up the policy and configure the transform action.
3. Configure the SCA component to invoke the endpoint exposed by DataPower

1. Creating an XML firewall

1. Log in to your DataPower box.
2. Select the XML Firewall icon as shown in Figure 2 below. The XML firewall service provides routing, security, filtering, and monitoring in a XML/SOAP architecture, while the Web service proxy provides these plus extended functionality within a Web services environment. A multi-protocol gateway connects client requests that are transported over one or more protocols to a back-end service that uses the same protocol or a different protocol. A Web application firewall provides security, threat mediation and content processing services for Web-based applications. The XSL Accelerator Service is used to optimize transformation of XML/SOAP with XSLT. Click Help any time during a task to access the online help, or click on the field label to view field-specific help.

   Figure 2. Create XML firewall

   
3. Click Add wizard to create a new XML firewall to display the Firewall Wizard screen:

   Figure 3. Configure XML firewall

   
4. Click Next to accept the default Pass Thru option, as the SOAP request should pass through the DataPower box:

   Figure 4. XML firewall wizard

   
5. Enter SoapRequestProcessor in the Name field and click Next:

   Figure 5. Enter name of firewall

   
6. Select loopback-proxy from the list of Firewall Types and click Next:

   Figure 6. Choose firewall type

   
7. Choose External_IP alias and port:

   Figure 7. Enter device address and port

   
8. The review page appears. Click Commit:

   Figure 8. Commit the configuration

   
9. The confirmation page appears. Click View Policy and the policy window will open:

   Figure 9. View Policy

   

2. Configuring the transform action

1. In the new policy window, drag the Transform icon onto the processing line between the two existing icons:

   Figure 10. Configure policy

   
2. Double-click the yellow highlights around the Transform icon. A new window opens.
3. On the Transform configuration page, upload the SoapRequest.xsl processing control file: click Upload, then select the file and you will be returned to the transform action screen, with the appropriate file selected as shown in Figure 11. Change the INPUT type and OUTPUT type:

   Figure 11. Configure transform action

   
4. Click Done and the XSL will be uploaded. You can download the XSL file below.

Step 3. Configure the SCA component to invoke the endpoint exposed by DataPower

1. The binding address of the Event validation component is changed to the endpoint exposed by DataPower:

   Figure 12. Invoke the endpoint exposed by DataPower

   

Conclusion

This article has shown you how to use a WebSphere DataPower SOA Appliance to process SOAP requests from an SCA component running on WebSphere Process Server. The DataPower appliance can be used to process SOAP requests at high performance rates, and the improvement is higher if a large amount of XML processing is involved.