Oracle Application Framework

Steps Required for Controller Extension in R12.2.X

The method to deploy controller & OAF components in pre-R12.2.x is much diffrent than in R12.2 onwards. Lets see how it is done.

Note:  This topic is not going to cover how to do controller extension, it only focus on changes deployment process for controller class files in version of R12.2 onwards.

R12.2.X moves away from conventional Oracle Application Server setup to Weblogic server and jar concept comes into the picture.

Recently, we wanted to do controller extension for one of our clients. We did controller extension and migrated the class file as we are doing in R12.1.3 version but pages failed each time. After lots of struggle we manage to run OAF page successfully. Below are the steps which we followed:

Step 1: Extend the require controller and give any name (for example: xxtest)

Step 2: move the above class file to the require product top under Java top (for example : $JAVA_TOP/oracle/apps/ak/attach/webui)

Step 3: Through personalization attach extended controller to OAF page

Step 4:  Generate the product jar file. This can be done by running ‘adcgnjar’ utility at unix box, it will ask for weblogic credentials. 

Note:  Since Credentials require at this step, normally DBA won’t  give it, so ask then to regenerate product jar where you place the file. Considering above example in step 2, I asked to regenerate “AK” product.

Step 5:  this step and below step (i.e. step 6) may not be necessary for you, but if your change won’t reflect or OAF page error out then run below script in putty if have an access else ask DBA to do so

    cd $ADMIN_SCRIPTS_HOME

     ./admanagedsrvctl.sh stop oacore_server1

     ./admanagedsrvctl.sh start oacore_server1

Step 6: Bounce the apache server.

Techie DK

Add comment