Manage the Copilot UI

This topic describes how to use the Transfer CFT UI, Copilot, to perform the following functions:

Start the Copilot UI

To begin a Transfer CFT graphical user interface session in a Windows environment:

  1. From the Start menu, select Axway software > Axway > Transfer CFT > Start Copilot server.
  2. Select Transfer CFT > Copilot User Interface from the Start menu, or open an Internet browser window and enter the URL using the format:
  3. http://host:port/index.html
  4. Where:
    • host: is the local host name or IP address of the Transfer CFT GUI (Copilot) server and can be replaced by the server host name
    • port: is the Transfer CFT GUI server port, and can be modified with the UCONF identifier [copilot.general.serverport] 
    • index.html: is the start page for the Copilot Java Web Start application (for transfer monitoring)
  5. The browser displays the login screen. After accessing the Transfer CFT GUI, you can add the URL to your Bookmarks.
  6. Enter your user name and password. For more information on user names and passwords, see your system administrator.
    NoteOn Windows systems, you can use the format user@domain, but domain cannot contain a dot extension (for example, user@domain.com).
  7. Click Confirm to start the user interface. The main Transfer CFT GUI window is displayed.
  8. If you enter an incorrect user name or password, you are prompted to re-enter this information.

Reconnect using the Copilot UI

When you log in, Transfer CFT is automatically started. If you disconnected from Transfer CFT, you can reconnect as follows:

  1. Select Connect to a new product from the File menu. The Connection to a Product window is displayed.
  1. Click Connect. The User Identification dialog box is displayed.
  1. Enter the User name and password. Click Ok.

Disconnect using the Copilot UI

To disconnect from Transfer CFT:

  1. From the Windows File menu, select the Disconnect from current product... command. Transfer CFT UI displays the disconnect confirmation window.
  2. Select Yes in the confirmation dialog box to end the Transfer CFT connection.

Display connection details using the Copilot UI

You can display the connection details while establishing a connection to your product. After you log in on:

  1. If you have not already done so, select Start Copilot Server from the Start menu, or complete the browser Address field to connect to Transfer CFT.
  2. Select Launch Copilot Graphical User Interface from the Start menu. The Connection to a Product window is displayed.
  3. All managed Copilot products are listed in the Connection to a Product window. Click the Details button for connection details.
  4. Click Connect.

The state of the plug-in connection process is displayed as the connection proceeds. The Connection details icon indicate either:

  • Status is okay
  • Skipped

Start the Copilot UI from a URL

Additionally, you can start the Copilot UI from a URL with additional parameters that over ride existing filter settings.

  1. Open an Internet browser.
  2. Enter the URL in the following format:

http://host:port/index.html?USERNAME=user&USERPASSWORD={CLR}password

Where:

  • host: is the local host name or IP address of your Copilot server and can be replaced by the server host name
  • port: is the Transfer CFT Copilot server port and can be modified with the UCONF identifier [copilot.general.serverport] 
  • user
  • password
  1. Add the log or catalog filter parameters.
  • Catalog filter parameters are described in detail in the topic Starting a catalog filter from a URL
  • Log filter parameters are described in detail in the topic Starting a log filter from a URL

How to define Copilot user profiles

To set user rights you can use either the PassPort AM, or configure the internal access management as described in Access management UCONF settings.

Troubleshooting

Copilot SSL connection to Central Governance does not work when FIPS is enabled

This issue occurs because the private key is encrypted using triple DES (by default). However, the certificate is encrypted using 40-bit RC2, which is not an approved FIPS algorithm. To remedy:

In OpenSSL use the pkcs12 -descert option to encrypt the PKCS12 certificate to triple DES (RC2-40). For example:

pkcs12-export -in <your server cert>.pem -inkey <your server key>.pem -out mycert.p12 -descert

Related Links