UC4 Scheduler (Atomic) is one of the best software scheduler on the market, recently acquired by CA.

In my case, UC4 is used for scheduling batch jobs for Oracle Retail and for the integration platform (Oracle Service Bus, JMS, AQ…).

It is a very scalable scheduler which in my case is executing more than 20.000 jobs per day. After 5 years of experience with UC4 Scheduler, I haven’t got many issues with it.

Besides providing a basis for RAC, Oracle Grid Infrastructure can be used to provide high availability framework for third party apps like UC4.

In this blog I’m not going to go through the every detail of how to configure UC4 Scheduler (Atomic), but just to reveal some ideas of how to control UC4 if you are using RAC or RAC One Node.

1.
You need to add UC4 app VIP address into /etc/hosts and Clusterware:

appvipcfg create -network=1 -ip=uc4_vip_address -vipname=uc4-vip -user=root -group=system

and start the resource:
crsctl start res uc4-vip

The same must be done for UC4 application in a similar manner. Here you can even create dependency between uc4-vip and UC4 Scheduler resources what I did in our production environment.

2.
You need to create action scripts, as user defined resources will be controlled by those script.

That script can be developed in various languages, but bash is capable and simple enough for this case.

It is important to note that you need to implement the following functions (interfaces):
– start
– stop
– check
– clean

This is just an excerpt from the action script:


function uc4_start
{
     if [ $USER == "uc4" ]; then
        #startso awcomm; sleep 5; startso watchworx; sleep 5; apachectl start; sleep 5
        startso awcomm; sleep 5; startso rmi; sleep 5; startso agentservice; sleep 5; startso watchworx; sleep 5; apachectl start; sleep 5
     else
        #sudo su - uc4 -c ". /opt/rtl/uc4/site/sosite; startso awcomm; sleep 5; startso watchworx; sleep 5; apachectl start; sleep 5"
        sudo su - uc4 -c ". /opt/rtl/uc4/site/sosite; startso awcomm; sleep 5; startso rmi; sleep 5; startso agentservice; sleep 5; startso watchworx; sleep 5; apachectl start;
 sleep 5"
     fi
}

After you setup all, UC4 will be automatically transfered to other node if the server will go down for some reason.

In addition, if server start, Clusterware will take care not only to start all resources, but to start it in right order.

If you follow my advice to create dependency between uc4-vip network resource and UC4 Scheduler app resource, Clusterware will start uc4-vip network first, and when it start successfully, it will start UC4 Scheduler.

I didn’t cover many steps in configuration and installation of UC4 as it will make this blog too long.

The main point is to understand that you can get much more for your money if you have enough knowledge to use existing functionalities.


Comments

There are no comments yet. Why not start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.