Transporter - Basic installation and connection questions

[Patricia Hindes]

We have never used or installed the Transporter before.  We are currently using Tidal 5.3x and are upgrading a sandbox environment to 6.2.  I have looked at all the transporter documentation I can find and am still missing some very basic questions - plus I cannot get the "help" option in transporter to work.

1. WHERE do you install the Transporter and why?  CM Server?  Master Server?  Desktop?  If it is on a server, then does the user that runs it need to remote the server in order to user transporter?
2. I have attempted to install on each of the above, but cannot establish a connection.  When I click "test" I get error "Failed to Connect [Login failure with responseCode [404]]What should I be entering in each of the following Connections fields?  My comments indicate what I have assumed/attempted to enter and received the error above.

• Connection name  - just a given name to a connection? aka TESSandboxMaster
• Server Name  - what server?  master?  Is there a specific format this needs to be in?
• DSP/Plug in name - I found a dsp file on my CM Server named TES-6.0.dsp - should I put TES-6.0 here?
• User - network user that is a Super user in Tidal?  aka networkname\superuser?
• pwd - windows pwd for that user?

Thank you for any help you can provide.

[Derrick Au · Accepted solution]

Hi Patricia,

1. The Transporter is installed on the Client Manager - the CM is essentially a web server to handle client requests, perform sacmd commands, and utility for transporting jobs from one environment to another. A Tidal user would have to be granted rights to Move Jobs to Production, and I believe Tidal user has to be able to sign on to the CM as well.

2. I've reviewed an older copy of the transporter user guide 6.1 provides instructions on how to complete those fields:

To create a connection: (on page 32)

•  In the Connection Name field, enter the name for the connection file.
• In the Server Name field, enter the name of the Client Manager machine.
• In the DSP/Plugin Name field, enter the master instance name.
• The master instance name is the TES DSP or Plugin name. This is displayed from the Web UI in the Master Status pane.
• In the Server Port field, enter the listening Web Service port used by the Tidal Web Client. The default is 8080 for non-secured connections and 8443 for secured connections.
• In the User and Password fields, enter a valid Enterprise Scheduler user name and password.
• Select the Secure HTTP option if you want to connect securely through the HTTPS protocol.

This option is enabled only if Transporter has been configured for secure
connections. Figure 8 is an example of Transporter not configured for secure
connections.
 

BR,

Derrick Au

[Patricia Hindes]

Thank you very much Derrick.  Your explanation as to the fields seems to make more sense.

In transporter - I remoted in the Client manager server and logged in as the tidal user - I changed my definitions and tried again and now get a slightly different error - "Failed to connect [Failed to get connect user for networkname\tidaluser on http://TESSandboxClient:8080/api/TES-6.0].  networkname\tidaluser  is Admin on TESSandboxClient and should have all the appropriate rights (logon, run as service, run as batch, etc).

In your reply, you state that the user needs to be "granted rights to move Jobs" - I don't see any information on this, but again... this is a super user in Tidal.  We are using a DEMO license right now, so I would suspect that license is ok.

Do you have any other suggestions with regard to the user?  Otherwise I will open a tac with Cisco and mark your reply as *correct answer*.

Thank you again for your help.

[Derrick Au]

Hi Patricia,

At this time, I would like to correct some information that was passed on to you earlier. The Transporter could be installed anywhere (ie, desktop, application server etc). All it really is another client running against the CM web server. Likewise, with the command utility. The CM handles the processing of sacmd requests.

I will go ahead and install Transporter and see what I can find out, but it's a good idea to raise a service ticket with Cisco Support at the same. BTW, where are you getting this error? In Transporter, there is a TEST button to test out your connections. This particular error message you are receiving pertains to a "connection problem" rather than a user authentication issue -- because if you supply an incorrect login and password, you will receive a different type of error message: "Logon failure"

BR,

Derrick Au

[Derrick Au]

Hi Patricia,

I was able to duplicate the error message Failed to connect [Failed to get connect user for: networkname\tidaluser on http://TESSandboxClient:8080/api/TES-6.0].

The Server Name should be the hostname of your client manager (if you specified Master, you will get [Login Failure with ResponseCode [404]].

Your DSP / Plugin name is incorrect. To make sure you are putting in the correct DSP / Plugin name, navigate to Master Status pane and the DSP / Plugin name will appear just right on top of the horizontal tabs (Overview, Queue, Fault Monitor, Connections, Messages).

For example,

Master Status - version 6.2.1.141    Plugin(your DSP/Plugin name is displayed here) - version 6.2.1.145

Also, it's case sensitive. DSP / Plugin name should be entered in exactly as it displayed from the Master Status pane.

Cheers,

Derrick Au

[Patricia Hindes]

Thank you for your guidance.  I am going to mark your first answer as correct because after I corrected the case of my dsp it connected!

thanks again.