Archive

Archive for July, 2009

RUP4 minor enhancements to Global Payroll

July 20th, 2009 Comments off

This is a brief summary on a couple of items of interest to Payroll users that are out in the latest RUP4 for EBS 11i. This information was presented at this year’s OHUG in Las Vegas. I have also posted this (as my first post) on the Oracle Contractors Network Blog

Generate Run Balance and Retro-Notification Report Performance

The first item is on the performance of the “Generate Run Balance” and “Retro-notification Report” processes, both of which have had their fair share of bad press on the performance front, especially with large payroll customers. The change is quite subtle: There is the addition of range PERSON_ID functionality which is designed to improve the performance of the cursor that generates the assignment actions. By enabling filter-at-source there is a reduction in the processing overhead in downstream processing.

This option is only activated via a parameter in PAY_ACTION_PARAMETERS. The parameter is RANGE_PERSON_ID which needs to be set to Y to enable the option. This makes its implementation quite neat, as it allows users to experiment to see whether performance gains are made. It also allows customers with multiple payrolls, of varying sizes, to target only their larger payrolls by use of Action Parameter Groups.

Balance Feed Purge

A couple of enhancements to the “Balance Feed Purge” concurrent program have been made. Firstly the purging operation run through the concurrent program has been made multi-threaded.

Secondly, a new parameter has been added to the program. The parameter is “Assignment Batch Size” – The default value is 1000. It has been provided to allow customers to specify the batch deletion commit unit size.

Retro Notification Report

An additional parameter has been added to the “Retro Notifications Report (Enhanced) – PDF”. The parameter is “Generate Report”. It provides a ’switch’ to prevent generation of the actual report!

This has been introduced to improve overall performance of the retropay activity when only the processing of the retro elements is required and that there is no requirement to analyze or review the data to be processed (by the report).

 

I did say it was a brief summary :)

I would like to thank and Acknowledge Brian Bellamy, Senior Director EBS Payroll and Localizations in Oracle, for providing the information in the first instance

Installing Oracle EBS R12 on CentOS 5.3 (part 2)

July 17th, 2009 2 comments

Shame on me for not getting around to this sooner! Thank you to those who took the trouble to comment on the first part of this ‘project’ – several of you have been asking for part 2 so hopefully your wait would not have been in vain…

So, as a recap. If you have gone through the steps featured in part one of this, you should have a machine with CentOS 5.3 installed, and with various settings configured ready for the Oracle install.

At the time of originally doing this install, the latest version of EBS was 12.0.4. I am aware that 12.0.6 and 12.1 are now out, however for the purposes of continuity I am proceeding with the 12.0.4 install. When I get around to doing it, I will document a 12.1 install.

Groups and Users

The following groups and users need to be created on the system. As these instructions assume a single-user/single-node installation of EBS we do not need an “applmgr” user. Execute the following commands as specified, from the “root” account…

groupadd oinstall
groupadd dba
groupadd oper
groupadd apache

Note that the apache group may already exist. Next we need to create the users and assign them to the groups…

useradd –g oinstall –G dba oracle
passwd oracle 
useradd –g oinstall –G apache apache
passwd apache

Again note that the apache user may already exist.

As can be seen, for my installation I have set the passwords to be the same as the usernames.

Create install directory

It is best practice to adhere to the Oracle Flexible Architecture (OFA) configuration for RDBMS / Applications installation directory structures irrespective of how your hardware may be configured. To this end you will need to issue the following commands (as the “root” account) which will create the top-level directory node into which the Oracle software will be installed…

mkdir –p /u01
chown –R oracle:oinstall /u01

Modify the Oracle user profile

Login as the oracle user and add the following to the end of the .bash_profile file. To modify this file ensure that your are in the default home directory of the oracle user…

cd

or

cd $HOME

Then issue…

vi .bash_profile

The chances are this file is empty or does not exist (so a new file will be created). These are the lines to add:

# Added for Oracle 10g
if [ $USER = “oracle” ]; then
  if [ $SHELL = “/bin/ksh” ]; then
    ulimit –p 16384
    ulimit –n 65536
  else
    ulimit –u 16384 –n 65536
  fi
fi

Create and set-up the stage area

Next step is to set up the installation stage area for the Oracle Applications software. For my install I executed the following steps as the “root” account, and then retro-applied directory permission changes afterwards to ensure that there would be no access issues later…

mkdir /StageR12
cd /StageR12

This is the start here directory

mkdir startCD

This is for APPL_TOP

mkdir oraApps

This is for RDBMS

mkdir oraDB

This is for Tools

mkdir oraAS

This is for databases

mkdir oraAppDB

Once this is done you then need to copy across the contents of the DVD’s / CD’s into the appropriate directories. The media is clearly labelled to assist. Note that this is a lengthy (and tedious) process. It should also be noted that there is (apparently) a PERL script that will do all of this for you. However I was unable to get this to execute correctly and so resorted to the manual methods above. Either way, you still need to be on hand to swap the media over as required. I would get a cup-of-tea and a good book to keep you company during this phase.

Once done you should end up with a stage directory structure that looks like this diagram:

EBS installation directory structure

EBS installation directory structure

 

Installing EBS

We’re now ready (at long last I hear you cry) to start the installation.

If you are not already in as oracle, log into your machine as the oracle user and open up a terminal session.

Start the Rapid Install Wizard by issuing the following commands:

cd /StageR12/startCD/Disk1/rapidwiz
chmod u+x rapidwiz
./rapidwiz

The following pages provide screenshots of typical rapidwiz install (although these are not the actual shots from my install – I was unable to screen-capture them!)

Welcome Screen

The rapidwiz executable will fire up a new GUI window. the first screen presented to you will be the welcome screen.

rapidwiz-1

 

 

Select Wizard option

The next screen enables you to select the wizard operation. By default the screen looks like this:

rapidwiz-2

 

 

However we wish to perform an Express Installation.

This sets up a fully configured single-user / single-machine system with a Vision Demo Database. By choosing to do an Express Installation the rapid install will use default values for many of the options. Check the “Use Express Install” checkbox and the click “Next”

Oracle Configuration Manager

Oracle Configuration Manager (OCM) is an optional component that is designed to facilitate support for your Oracle products. OCM provides continuous tracking of key Oracle and system statistics of the machine it is running on. The data collected by OCM is sent via secure HTTPS back to Oracle Support.

rapidwiz-3

 

It is strongly recommended that you check the “Decline” checkbox. Remember that we are installing a trial / demo system for our own training purposes, and as such are not an officially licensed Oracle Applications Client! Click on the “Next” button.

Express Configuration Manager

The express configuration information screen prompts for minimal configuration values. Default values are provided for all fields.

rapidwiz-4

 

In order for the install to proceed you will need to amend the Base Directory entry. Remember that earlier we created the top-node “/u01”? Click into the “Base Directory” entry box and replace the default “/d01” with “/u01”

The screen will automatically amend the entry in the Instance Directory field.

rapidwiz-5

 

You can now click on the next button.

Validate System Configuration

Rapid install runs and displays a series of pre-install tests.

rapidwiz-6

When the tests are complete then the pre-install check screen is displayed.

rapidwiz-7

If there is an exclamation mark or X icon shown click on it to see the details stored during the checking process.

You may proceed with the installation if there are any exclamation marks or X icons shown, however the rapid install process will warn you with an alert screen. You are on your own if you do proceed however!

Assuming all is well with the pre-installation checks then you can click on the Next button to proceed with the installation.

Review and start the installation

You will be presented with the installation review screen…

rapidwiz-8

Click on the next button

rapidwiz-9

Click on the Yes button to proceed

Installation in progress

Whilst the installation is in progress you will see a progress screen similar to the one shown below…

rapidwiz-10

You will be prompted at intervals to point rapid install at the filesystem location for the various install stage directories that we created earlier.

The installation on my machine took approximately 90 minutes to complete. This will vary depending on the machine resources and also whether you stage directories are on the PC or held on an external drive.

Post-install and finish rapidwiz

Assuming all the post install checks are successful you will see the following screen:

rapidwiz-11

If any issues occur during the installation then you will see one or more X icons against the areas of concern. All being well you can click on the next button.

rapidwiz-12

Click the finish button to exit the Rapid Install Wizard.

Post-installation tasks

There are a surprising number of post installation tasks that need to be carried out before you can really start to use the system.

I am not entirely sure of the correct sequence that these tasks need to be completed, so I have documented them in the order I executed them in. Apart from the Java/JRE issues that I encountered (see later) most other things seemed to go smoothly.

Modify the oracle shell profile

You need to modify the shell profile for the oracle user to ensure that all of the environment settings are correctly initialized upon login.

You would also need to perform this step if you plan to create and user other accounts on your machine (such as a named user account for development tasks).

Edit the .bash_profile file under the oracle user’s home directory. Open a terminal session.

cd $HOME
vi .bash_profile

You will need to add in the following extra lines at the end of the script.

# Additional items to set path for EBS
DB_HOME=/u01/oracle/VIS/db/tech_st/10.2.0; export DB_HOME
APPL_TOP=/u01/oracle/VIS/apps/apps_st/appl; export APPL_TOP
COMMON_TOP=/u01/oracle/VIS/inst/apps/VIS_localhost; export COMMON_TOP
# Now set environment
. $APPL_TOP/APPSVIS_localhost.env 

Create start-up and shut-down scripts

Obviously there are supplied scripts to start-up and shut-down the various services, however the following scripts make it a lot easier to shut down and start up the environment. I created 2 scripts, located in the home directory of the oracle user.

The ‘start_VIS.sh’ script looks like this…

# commands to start EBS
cd $DB_HOME
. ./VIS_localhost.env
cd $DB_HOME/appsutil/scripts/VIS_localhost
# start the listener
./addlnctl.sh start VIS
# start the database tier
./addbctl.sh start
cd $INST_TOP/admin/scripts
# start EBS services (apps tier)
./adstrtal.sh apps/apps
# start the internal conc manager
./adcmctl.sh start apps/apps

 and the ‘stop_VIS.sh’ script looks like this…

 # commands to shutdown instance
cd $INST_TOP/admin/scripts
# stop all EBS services (apps tier)
./adstpall.sh apps/apps
cd $DB_HOME
. ./VIS_localhost.env
cd $DB_HOME/appsutil/scripts/VIS_localhost
# stop the listener
./addlnctl.sh stop VIS
# stop the database
./addbctl.sh stop immediate

Make sure that you make these scripts executable by issuing the following commands:

chmod u+x start_VIS.sh
chmod u+x stop_VIS.sh

To run either, simply type

./start_VIS.sh

etc

Verify the OAM portal page

Once the installation is complete, the Oracle Applications manager portal page (formerly known as the rapid installation portal) can be accessed using the following information:

URL: http://localhost.localdomain:8000/OA_HTML/AppsLogin

Username is SYSADMIN and the password is SYSADMIN

The front screen of the portal looks something like this…

oam-portal

Apply latest JDK update

I came across several on-line references that suggested that I should apply the latest JDK/JRE versions to the apps tier and also install JRE on the database tier to ensure that the apps tier and DB tier match.

The Metalink note 384249.1 provides excellent details on how to upgrade the JDK on the apps tier, so I’ll not repeat them here, however it is an important post-install step.

Personally, I chose not to go with JDK 6.0 but stuck with JDK 5.0. I used JDK 5 update 13 (15013) simply because I already had the downloaded files to hand. All current and historic versions of JDK are downloadable from Sun. Whichever version you decide to go with you will need to use the FND_TOP program txkSetPlugin.sh to ensure that the correct JRE version is then updated into the various apps scripts.

References

Since this was quite a learning curve for me I did make extensive use of a variety of online resources to aide in the performing this install (and the post install steps). The ones from memory are as follows (and are in no particular order or importance, unless indicated)…

  • Oracle Applications: Installation Guide using Rapid Install – Release 12 part number B31295-07
  • Oracle Applications Installation and Upgrade Notes Release 12 for Linux (32-bit) – metalink note 402310.1
  • Oracle Applications Release Notes Release 12 – metalink note 405293.1
  • Using Latest update of JDK 5.0 with Oracle E-Business Suite Release 12 – metalink note 384249.1
  • Overview of using Java with Oracle EBS Release 12 – metalink note 418664.1
  • R12 Rapidwiz post install step HTTP, Login page, Virtual directory, JSP, Help page fails – metalink note 414414.1
  • Installation notes – JDK 5.0 Linux (32-bit) – http://java.sun.com/j2se/1.5.0/install-linux.html
  • Manual Installation and Registration of Java Plug-in – linux – http://java.sun.com/j2se/1.5.0/manual_install_linux.html

The following OTN forum posts were read and whilst may not have been directly relevant did help to steer me down the correct paths to investigate various issues, especially with JRE and the apps forms. In particular, the first reference was very useful. Without it I would have not known about the txkSetPlugin command…

  • Forum Home >> E-Business Suite >> Technology – EBS on Linux
    Thread: EBS Client Running on Linux, posted by Glen Palmer on 27th May 2008
  • Forum Home >> E-Business Suite >> EBS General Discussion
    Thread: EBS forms not opening in Linux client machine