RA JD Edwards Agent Administration

The basic steps for implementing the RA JD Edwards Agent solution include:

  1. Setting up the runubexml and runube commands.
  2. Creating a database user with necessary permissions and synonyms.
  3. Loading the RA JD Edwards Agent.jar file into the Automation Engine.
  4. Creating RA JD Edwards Agent JDBC and program Connection objects.
  5. Defining an RA JD Edwards Agent on the JD Edwards machine.
  6. Creating an RA JD Edwards Agent solution Agent object.
  7. Creating RA JD Edwards Agent UBEXML and UBE Jobs.

Setting up the runubexml Command for UBEXML Jobs

The RA JD Edwards Agent uses the JD Edwards runubexml and runube API commands to submit reports for UBEXML and UBE Jobs; therefore the runubexml and runube commands must be set up properly and work from where the Agent will execute them.

The runubexml and runube programs are executed as commands by the Agent. These program are found on the server in the JDE system, bin32 directory.

The best way to first test the commands is to execute them in the system, bin32 directory. Once you are satisfied that the commands work, a Windows PATH or a UNIX ENV setting can be made, so the commands can be executed in the Agent's directory. When executing runubexml and runube programs, documents will be put in the directory or path that you execute the program in.

To execute the runubexml and runube program in another directory besides the bin32 directory, the Windows path or UNIX environment setting may have to be changed. On the server, the Windows PATH or UNIX ENV must point to the JDE directories:

  • bin32
  • lib32
  • libv32

All of the above directories are necessary to run the programs in another directory besides the system, bin32. The XML documents will be put in the directory where the runubexml and runube programs are executed. The LD_LIBRARY_PATH environment variable may need to be set as well.

For more information, consult the JD Edwards documentation concerning the runubexml and runube API commands.