Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "How to "Smoke Test" the new technology agent controller"
| Line 5: | Line 5: | ||
== Set up environment variables. == | == Set up environment variables. == | ||
| − | + | <OL> | |
| − | + | <LI> | |
| − | + | <TT>cd <ac>/lib; export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH</TT> | |
| + | <LI> | ||
| + | <TT>cd <ac>/bin; export PATH=`pwd`:$PATH</TT> | ||
| + | <LI> | ||
| + | <TT>export PATH=<path to the correct Java bin>:$PATH</TT> | ||
| + | </OL> | ||
Note that "the correct Java" is something to think carefully about! It's an important factor to document to ensure thorough testing. | Note that "the correct Java" is something to think carefully about! It's an important factor to document to ensure thorough testing. | ||
| Line 13: | Line 18: | ||
Note that if you're running 32-bit apps on a 64-bit system, you're in for a rough ride separating out the two environments! | Note that if you're running 32-bit apps on a 64-bit system, you're in for a rough ride separating out the two environments! | ||
| − | == Set up your <ac>/config/serviceconfig.xml file (it's empty on delivery) by running ./SetConfig.sh (you '''are''' still in the <ac>/bin directory, right?). You can Accept defaults for all values (unless you know you want to test security, or remotely from another system, etc.). == | + | == Set up your <TT><ac>/config/serviceconfig.xml</TT> file (it's empty on delivery) by running <TT>./SetConfig.sh</TT> (you '''are''' still in the <TT><ac>/bin</TT> directory, right?). You can Accept defaults for all values (unless you know you want to test security, or remotely from another system, etc.). == |
| − | == Edit <ac>/agents/*/agent.xml, remove all ".\" prefixes and ".exe" suffixes from all launchinfo lines. == | + | == Edit <TT><ac>/agents/*/agent.xml</TT>, remove all "<TT>.\</TT>" prefixes and "<TT>.exe</TT>" suffixes from all launchinfo lines. == |
== Make sure an AC is not running already: == | == Make sure an AC is not running already: == | ||
| − | + | <OL> | |
| − | + | <LI> | |
| − | + | <TT>ps aex | grep -i server</TT> | |
| + | <LI> | ||
| + | <TT>ls -last /tmp/IBMRAC</TT> (clean it out if stuff is there) | ||
| + | <LI> | ||
| + | <TT>ipcs</TT> (to see if there are unattached shmids! if so, su to root and ipcrm the shmids) | ||
| + | </OL> | ||
== Start the agent controller. == | == Start the agent controller. == | ||
| − | It's important to use the ACStart.sh script now. | + | It's important to use the <TT>ACStart.sh</TT> script now. |
| + | |||
| + | == Check the AC for minimal functionality: run "<TT>./SampleClient</TT>" == | ||
Revision as of 13:41, 25 September 2006
Contents
- 1 Download the agntctrl and sdk packages for each given system, create subdirectories for holding the release packages, and unzip them there.
- 2 Set up environment variables.
- 3 Set up your <ac>/config/serviceconfig.xml file (it's empty on delivery) by running ./SetConfig.sh (you are still in the <ac>/bin directory, right?). You can Accept defaults for all values (unless you know you want to test security, or remotely from another system, etc.).
- 4 Edit <ac>/agents/*/agent.xml, remove all ".\" prefixes and ".exe" suffixes from all launchinfo lines.
- 5 Make sure an AC is not running already:
- 6 Start the agent controller.
- 7 Check the AC for minimal functionality: run "./SampleClient"
Download the agntctrl and sdk packages for each given system, create subdirectories for holding the release packages, and unzip them there.
There is some debate about whether to overlay the runtime and sdk packages or keep them separate. My fear with overlaying is that you're likely to miss any error in either package if it is masked by the other. Therefore, I put the agntctrl package in <ac> and the sdk package in <sdk>.
Set up environment variables.
- cd <ac>/lib; export LD_LIBRARY_PATH=`pwd`:$LD_LIBRARY_PATH
- cd <ac>/bin; export PATH=`pwd`:$PATH
- export PATH=<path to the correct Java bin>:$PATH
Note that "the correct Java" is something to think carefully about! It's an important factor to document to ensure thorough testing.
Note that if you're running 32-bit apps on a 64-bit system, you're in for a rough ride separating out the two environments!
Set up your <ac>/config/serviceconfig.xml file (it's empty on delivery) by running ./SetConfig.sh (you are still in the <ac>/bin directory, right?). You can Accept defaults for all values (unless you know you want to test security, or remotely from another system, etc.).
Edit <ac>/agents/*/agent.xml, remove all ".\" prefixes and ".exe" suffixes from all launchinfo lines.
Make sure an AC is not running already:
- ps aex | grep -i server
- ls -last /tmp/IBMRAC (clean it out if stuff is there)
- ipcs (to see if there are unattached shmids! if so, su to root and ipcrm the shmids)
Start the agent controller.
It's important to use the ACStart.sh script now.