I have a HP RGS Receiver v7.1 installed on my desktop which initiates a remote Session to my RHEL based workstation running HP RGS sender deployed in a LAN. Now when launching the HP RGS Receiver it brings up a window asking for the host name or IP Address of the PC to connect to (in this case the RHEL box). When provided the hostname, the next question asked is the username and the password. When all these detials are provided, the connection is successfully established and all works as expected. I am trying to autolaunch the HP RGS Receiver so I can bypass entering the hostname or ipaddress, username and password during each launch. When reading the usermanual, there is clearly a way of doing this by using the HP RGS commandline autolaunch properties. The property Rgreceiver.Session..IsConnectOnStartup should allow me to setup autolaunch while I provide the hostname,username and password int he following properties: Rgreceiver.Session.n.Hostname Rgreceiver.Session.n.Username Rgreceiver.Session.n.Password Rgreceiver.Session.n.PasswordFormat So it is assumed that when I pass these as command line options while launching the HPRGS executable rgreceiver.exe it should all read the values from the command line and directly establish the connection without me having to enter these details. However it does not seem to work I assume that in n we specify the session number = 1 (because we are working with only a single session) The command Rgreceiver.exe -Rgreceiver.Session.1.IsConnectOnStartup=1 -Rgreceiver.Session.1.Hostname="MyHostName" -Rgreceiver.Session.1.Hostname="MyUserName" -Rgreceiver.Session1.Password="mypassword" -Rgreceiver.Session.1.PasswordFormat=Clear does not seem to have any impact. The HPRGS software behaves the same with or without command line and sending in the commandline does not seem to have any impact on the way it launches neither it gives any error. I have tried to above command line through multiple ways (for e.g. using delimetes and without delimiters, using different values for session number and so on) but it seems Rgreceiever does not even recognize that the commands were given in the first place. I have run out of all options. Any help will be appreciated.
I'm not sure why the command line parameters are not working, but you might want to try to put these same settings into an xxxxx.rgreceiver file. When you double-click the .rgreceiver file, the RGS Receiver will launch with the settings contained in the file. It's worth a try to see if works better for you. (This is described in the RGS User Guide in a section called "Auto-launching connections.")
This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.