Running the worklist!

This post is part of series on building a custom worklist for BPM/SOA 11g.

First of all, congratulations on making it all the way through the walkthrough!  Whether you built the code yourself or downloaded it from Subversion, by now you must be ready to deploy it to your test environment and try it out!

The Maven POM that we created included all of the necessary information for the WebLogic Maven Plugin that we installed to build, package and deploy our worklist to our BPM server instance.

The worklist sample has been built to run on the soa_server1 managed server in your BPM domain, i.e. the one that BPM is running on.  If you used a developer install, this will be the AdminServer instead.

If you have not done so already, go back to your POM and make sure you have the correct details in there for your server environment, then type:

# mvn deploy

This will cause Maven to build the worklist, package it up into a WAR file (which it will place in the target directory), deploy it to your server and publish it into your local Maven repository.

If you are not using Maven, then you can always deploy the WAR file using the WebLogic Server console.

Once that is done (it should take about a minute or so) you should be able to access your worklist at http://yourserver:8001/worklist (substitute in your own server and port).

Go ahead and log in using a user defined in WebLogic.  If that user has some tasks assigned to them, you should see them show up in your Task List View.  Go ahead and look at the Initiate Tasks View and try initiating a task.

If you don’t already have some tasks to play with, you will want to go into JDeveloper and create yourself a composite with a BPEL or BPMN process in it and some Human Tasks, and assign them to your user.

For a task to show up in the Initiate Tasks View, it will need to contain a Human Task of the type ‘Initiation,’ probably as the first task in the process, and you will need to create a Task Form.  The easiest way to do this is to use the Auto-Generate Task Form option in JDeveloper.  As we discussed earlier, make sure you create the Empty1 page in the adfc-config unbounded task flow in your Human Task projects too.

Well, there you go, a working custom worklist application.  Have fun extending it, or using what you have learnt to build your own custom worklist.

Remember to come back from time to time (or use the link on the right to subscribe) to get updates as we make enhancements to the sample.

About Mark Nelson

Mark Nelson is an Architect (an "IC6") in the Fusion Middleware Central Development Team at Oracle. Mark's job is to make Fusion Middleware easy to use in the cloud and at home, for developers and operations folks, with special focus on continuous delivery, configuration management and provisioning - making it simple to manage the configuration of complex environments and applications built with Oracle Database, Fusion Middleware and Fusion Applications, on-premise and in the cloud. Before joining this team, Mark was a senior member of the A-Team since 2010, and worked in Sales Consulting at Oracle since 2006 and various roles at IBM since 1994.
This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

One Response to Running the worklist!

  1. Pingback: Running the worklist!

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s