Parameters Checklist Setup

After you install the Tivoli Adapter package, the setup script prompts you for the following information:

• Tivoli Adapter port number – The default is port 2323. However, if port 2323 conflicts with another application that is using that port, you can specify a different port when prompted.

• Tivoli Policy Region – The script prompts you for the Tivoli Policy Region in which the Sun Management Center Task Libraries should be created. The policy region must already exist, or the script will fail.

• Tivoli Event Server – Prompts you to restart the Tivoli Event Server. Restarting the Tivoli Event Server is required for the new Sun Management Center rule base to be recognized by Tivoli. If you choose not to have the installation script restart the server, you must restart the server manually before the integration will function correctly.

  Ensure that the Tivoli Event Server restarts successfully and without errors. If the Event Server doesn't restart successfully, neither the adapter nor the SyMONInt application can be started by using the installation script. You will need to perform these steps manually.

• TEC Adapter – If you want the installation script to start the TEC adapter, answer yes. If you answer yes, the adapter will be started by invoking the $BINDIR/TME/TEC/adapters/bin/tecad_symon executable.

  ---

  Note –

  If the TEC adapter does not start successfully, the SyMONInt application cannot be started automatically. You will need to perform these steps manually. See Starting the TEC Adapter and SyMONInt Applications Separately

  ---

• SyMONInt startup application – Prompts you to start the SyMONInt startup application. If you answer yes , the script /opt/SUNWsymon/addons/Tivoli/sbin/si-start.sh is run. This application must be running in order for the integration to work correctly. If you choose to not have the installation script start the application, you must start the application manually.

  You will need to restart the SyMONInt startup application in the following instances:

  • After rebooting the system

  • If the process dies

  • If the process is killed by manually running the si-start.sh program