Check BRM patch version

To check the latest patch installed on Oracle BRM:

Infranet: Type 'pinrev' or check pinrev.dat
Pipeline: Check 'version.info.txt' in $IFW_HOME

To be sure that these files are current, the patches must be installed using the installer. These files might not get properly updated if, for example, instead of running the installer, you extract the new files from the tar file and then just plunk them in their respective directories.

Migrating IPL files

The following are common causes of IPL files throwing errors when committing them in production after taking them from a test/integration environment:

• The resources and GL/IDs used by products and discount rules in the IPL file does not exist in production.
• The discounts mentioned in the deals are not included in the IPL file to be committed.
• The service used by the products in the IPL does not exist in production.
  

Failover CM hosts in Java apps

To make sure that your Java application only connects to one CM server, take out the failover entry in the Infranet.properties file.

This has caused a lot of grief with a colleague because he was canceling products thinking he was connected to a test environment but was actually connected to production. The test environment was down and he had a failover entry for the production environment in his properties file.

To avoid this situation, better comment this entry (Infranet.failover.nn) out.