Contenu connexe
Similaire à Rit 8.5.0 training cloud instructions
Similaire à Rit 8.5.0 training cloud instructions (20)
Rit 8.5.0 training cloud instructions
- 2. RATIONAL INTEGRATION TESTER 8.5.0 CLOUD INSTRUCTIONS
2 Provisioning instances
If you have created instances of the Windows cloud images that were provided for GH Tester 5.4 or
for Rational Integration Tester 8.0, then the process of creating instances will be familiar. As the
instances now run on Linux, there are a few changes, which are detailed in this section.
1. First, you will need to log into your Rational Demo Cloud account at
http://www.ibm.com/cloud/enterprise/. Once you have logged in, you should see the
console. Go to the Instances tab to see what instances you currently have available.
2. In this screen capture, no instances are in use, though you may have some already. Check
that you have not reached your limit in terms of instances. If you have, you will need to
remove an instance before continuing. Otherwise, you can just click Add Instance.
3. You’ll now need to search for the appropriate image. In the search boxes, select shared
images, the Ehningen data centre, and any architecture, then click the arrow button to
search for instances.
Page 2 © IBM Corporation 2001, 2013
- 9. RATIONAL INTEGRATION TESTER 8.5.0 CLOUD INSTRUCTIONS
3 Connecting to instances
3.1 Initial conection
1. In the Rational Demo Cloud console, select your instance. Below, you should be able to see
the IP address and the URL for the instance. Copy and paste either one of these to your
clipboard.
2. Open your remote desktop software. On Windows 7, this can be found at Start > All
Programs > Accessories > Remote Desktop Connection.
3. The software will need a URL or IP address, so paste the one that you copied in step 1. No
username or password is required at this stage; you will enter these after connecting.
4. Click Connect.
Page 9 © IBM Corporation 2001, 2013
- 10. RATIONAL INTEGRATION TESTER 8.5.0 CLOUD INSTRUCTIONS
5. You may receive a warning here about the identity of the server; as the Linux software we
are using does not support this newer feature of the remote desktop protocol, this is
expected, so click Yes to continue.
6. When you connect, you should see a login screen with three options: a module, a username,
and a password. As this is the first time you’re connecting to the instance, leave the module
set to initial_session. Enter rational as the username, and the password that you set for
that user when creating the instance.
7. Click OK. A window will appear on the left side of the window. It should state that it is
connecting to your host on port 5910. If it says a different port, such as 5911 or 5912, take
note of this for later on.
Page 10 © IBM Corporation 2001, 2013
- 13. RATIONAL INTEGRATION TESTER 8.5.0 CLOUD INSTRUCTIONS
Rational Integration Tester itself can be accessed through a link on the desktop, while the Rational
Test Virtualization Server and the Rational Integration Tester Platform Pack HTTP Proxy have both
been set up to run as services, and so you should not need to change anything there.
3.3 Disconnecting and Reconnecting
Rather than logging out, it is easier to disconnect the remote desktop session; this will leave your
programs running for the next time you connect.
When you want to reconnect to your session, the procedure is slightly different from the initial
connection: until you see the login screen on the remote machine, the procedure is the same as
before. However, at the login screen, you should choose the resume_session module, and enter
your user name and password. You will notice that it also suggests a port: 5910 is the default. If this
matches what you saw previously on your initial connection, leave it alone, but on some occasions,
you may need to change this to 5911, 5912, etc. This usually only happens if something went wrong
with the initial connection. As the port numbers increment by one, it should not take long to find
the correct port anyway.
Page 13 © IBM Corporation 2001, 2013
- 14. RATIONAL INTEGRATION TESTER 8.5.0 CLOUD INSTRUCTIONS
4 Troubleshooting
4.1 Connection issues
If you can’t connect to the remote machine at all using the remote desktop, then it may be worth
trying to connect to that address over SSH. If you can’t connect at all (there’s no need to worry
about logging in), then it may be that something has gone wrong with the machine, or that your
firewall is blocking traffic to that machine. Check the URL or IP address used as a first step; you can
also try rebooting the remote machine through the SmartCloud console. If neither of those work,
you may have a firewall issue.
If you can connect via SSH, but not by remote desktop, then it is possible that the remote desktop
server is not running. The easiest way to fix this is again restarting the VM. If that doesn’t work,
check the firewall.
At times, you may connect to the remote machine successfully, but the login fails. If this happens,
simply try again, as it does occasionally fail on the first connection; subsequent connections are
usually fine.
4.2 Keyboard issues
The remote desktop software used on the Linux instances, xrdp, can be somewhat limited in its
support for different keyboards. Efforts have been made to improve the native coverage of the
keyboard support used here, but this has not been tested, as we don’t have access to every different
type of keyboard that could be used. If you have problems with the keyboard, send an email to Matt
Tarnawsky/UK/IBM with a description of the issue. If you are using Windows, make sure you
include the regional information used on your local machine. On Windows 7, this can be found by
going to the Region and Language section of the Control Panel, then selecting Keyboards and
Languages, clicking Change keyboards, and finally taking a screenshot of the information
displayed:
Page 14 © IBM Corporation 2001, 2013
