If I have problems with building Aion apps, like a coredump for example, and the problem can be traced back to the licensing files in /ca_lic, what is the easiest way to correct this problem?
search cancel

If I have problems with building Aion apps, like a coredump for example, and the problem can be traced back to the licensing files in /ca_lic, what is the easiest way to correct this problem?

book

Article ID: 65911

calendar_today

Updated On:

Products

Aion Business Rules Expert

Issue/Introduction

You will have to obtain an updated copy of the licensing software from the support portal, assuming your userid has access authority or you can open an issue with Global Support

 

Environment

Release:
Component: AIONM

Resolution

STEP 1: INSTRUCTIONS - For all platforms.

First make a backup copy of your existing CA.OLF file located in the CA_LIC directory of the machine(s) in question. Name the backup OLDOLF.BKP.

Copy the contents of this <license.txt> file and append it to the bottom of the original CA.OLF file on the machine that is experiencing the licensing error.

Save the newly updated CA.OLF file and the change will take effect immediately (it is not necessary to either reboot your machine or recycle the licensed product).

If you have any questions regarding this procedure, please contact your CA Technical Support representative for the product in question.

STEP 2: INSTRUCTIONS - Follow the steps for AIX 5.1 sp 3.

INSTRUCTIONS
For AIX Platform
Download the file lic98aix.tar.z into a temporary directory called /TEMP (note, it should be '/' and not '\' which is for Windows).

Stop all Broadcom Enterprise products on your machine.

Go to the /TEMP directory and uncompress the file: uncompress lic98<platform>.tar.z

Backup all the files under /ca_lic directory.

Copy the uncompressed file from Step 3 to /ca_lic directory.

Untar the file: tar xvf lic98<platform>.tar

Run the 'install' script (either 'install' or as './install')

Copy the ca.olf file from the backup you made in Step 4 to the /ca_lic directory and make sure it is owned by 'root' with file permissions of at least 644.