To route and record HTTP(S) and TCP traffic with Rational® Test Control Panel and Rational Integration Tester,
start the HTTP/TCP proxy. If the proxy is installed as a Windows service,
you can configure it for automatic startup on boot or for manual startup
on demand.
About this task
On Windows systems,
the HTTP/TCP proxy is, by default, configured to be installed as a
service, and for automatic startup on boot. If you cleared these selections
during the installation, then use the
IBM® Installation Manager Modify
option to update the installation.
Procedure
Starting and stopping the HTTP/TCP proxy on Windows:
- To start the proxy, from the command line, run the startup.bat file
from the default location C:\Program Files\IBM\RationalTestControlPanel\httptcp.
- To stop the proxy, close the Terminal window.
- If the proxy is installed as a Windows service:
- To start the service, from the Start menu, click .
Note: By default, the proxy is configured to start automatically
on boot.
- To stop the service, from the Start menu, click .
Tip: You can also open the Services window
in Control Panel, right-click .
- To modify the Windows service
from automatic startup to manual startup:
- Go to Control Panel, and select .
- Right-click IBM RIT HTTP Proxy Windows
service.
- Click Properties and change the
startup type from Automatic to Manual.
Click OK.
Tip: - You can also use this Control Panel option to start, restart,
or stop the service.
- You can also run editProxyService.bat from
an Administrator command prompt and change the startup type, start,
restart, or stop the service on the General page.
Starting and stopping the HTTP/TCP proxy on non-Windows
systems
- To start the proxy, from the command line, run the startup.sh file
from the default location: /opt/IBM/RationalTestControlPanel/httptcp.
- To stop the proxy, close the Terminal window.
Configuring automatic start on boot on non-Windows systems:
- Ensure that you have root permissions.
- Add the startup.sh script to the path /etc/init.d.
- Create symbolic links to the script in the run-level folders,
for example, /etc/rc3.d.