Archive for the ‘Atrium Integration Engine’ Category

Set AIE 7.6.04 up on its own RPC Port

Tuesday, October 18th, 2011

To set AIE onto its own RPC Port, you will need to add in a new RPC port number to the ARSystem, update the aie.cfg file, and restart the ARServer and AIE services so that the changes can take effect. By putting AIE onto its own port number, this helps to prevent the rest of the system from experiencing performance issues when your AIE jobs are running.

The steps to complete this task are as follows (the following steps are under Linux/Unix):

  1. Open the AR System Administration Console and navigate to Server Information.
  2. Change to the Ports and Queues tab.
  3. In the table, locate an empty line and enter in an RPC Prog Number, Min Threads, and Max Threads values.
  4. Apply the changes.
  5. From the server, stop AIE and the ARServer.
  6. Navigate to where the aie.cfg file is located and open it up in a text editor. If you used the default install, this should be located at:
    • /opt/bmc/AtriumCore/aie/service/conf/aie.cfg
  7. Part way down you should see a section for “PrivateRPCPort:”. On this line, add in the RPC port you defined above.
  8. Save your changes.
  9. Restart your ARServer. You had to do the stop/start in order for the new port numbers to take effect.
  10. Restart you AIE instance. It will start up using the new details.

 

AIE 7.6.04 Failed to Load Adapter Error

Thursday, September 1st, 2011

After running the aie001 start-up script for your first instance, if you look at the ./AtriumCore/aie/service/log/Inst_001_aiemain.log file, you may see the error:

  • [Thu Sep  1 2011 10:03:36.3840] BMC Atrium Integration Engine Version: 7.6.04 SP1 201104201700 (EIEMSG 3309)
  • [Thu Sep  1 2011 10:03:36.3840] Remedy Link starting to process requests Thu Sep  1 10:03:36 2011 (EIEMSG 3301)
  • [Thu Sep  1 2011 10:03:36.6820] Adapter :  (EIEMSG 3338)
  • [Thu Sep  1 2011 10:03:36.6820] Adapter :  (EIEMSG 3338)
  • [Thu Sep  1 2011 10:03:36.6890] Adapter : Failed to load adapter  (EIEMSG 3330)

After some investigation, it turns out is was due to the AIE_ORACLE_LIB_DIR=”.” variable at the top of the start-up script. The start-up script takes this value, which should point to your Oracle/DB2 client directory depending on which adapter you are using, and adds it into the LD_LIBRARY_PATH.

Even if you have the values for the LD_LIBRARY_PATH defined in your environment, they do not show up for use in the script. To prove this, add “echo $LD_LIBARY_PATH” into the start-up script, below the “export LD_LIBRARY_PATH” line. Running the script with the change, you will see the LD_LIBRARY_PATH echoed to the screen:

  • /apps/infra/ar/AtriumCore/aie/service/bin:./lib:./lib64

Updating the start-up scrpit to something as follows (this is the path to our Oracle client directory):

  • AIE_ORACLE_LIB_DIR=”/ora/fs0000/s00/oracle/product/10.2.0.3″

Restarting our instance, and then checking the log file again, we can see that we no longer get an Adapter error:

  • [Thu Sep  1 2011 10:05:54.7430] BMC Atrium Integration Engine Version: 7.6.04 SP1 201104201700 (EIEMSG 3309)
  • [Thu Sep  1 2011 10:05:54.7440] Remedy Link starting to process requests Thu Sep  1 10:05:54 2011 (EIEMSG 3301)

The following shows the two changes we made to all our aie00X scripts:

start_instance() {
AIE_ORACLE_LIB_DIR=”/ora/fs0000/s00/oracle/product/10.2.0.3
echo “WARNING : Please make sure that AIE_ORACLE_LIB_DIR is set to point to Oracle client directory if you are going to use Oracle Adapter.”
AIE_DB2_LIB_DIR=”.”
echo “WARNING : Please make sure that AIE_DB2_LIB_DIR variable is set to point to DB2 client directory if you are going to use DB2 Adapter.”

unset ORACLE_HOME

LD_LIBRARY_PATH=/apps/infra/ar/AtriumCore/aie/service/bin:${AIE_ORACLE_LIB_DIR}/lib:${AIE_DB2_LIB_DIR}/lib64
export LD_LIBRARY_PATH

echo $LD_LIBRARY_PATH

NOTE:  If your not using DB2, then you should also remove the “:${AIE_DB2_LIB_DIR}/lib64” from the end of the LD_LIBRARY_PATH as hi-lighted in red above.