Installing Managers

The Signiant Manager automates and controls the movement of digital content within and between organizations. The Manager is installed on a server to coordinate and log the data transfer activities carried out by a collection of Signiant Agents. Agents are installed on remote computer systems and are responsible for the actual transfer of data.

Installation Prerequisites

• Ensure that your system meets Manager+Agents System Requirements.
• Record the following information required during installation:
  • Organization Name
    • User Account Name
    Linux default: root
    Windows default: NT Authority\system
    If the system is accessing data across a network, it is recommended that you create a new account within your Active Directory or domain and verify that you can transfer files while logged in using this account.
    • Domain Name
    • Mail Server Name
    • Locality Information - City and State/Province where the Manager is installed
    • CA Passphrase
• On Linux, disable ipv6 in /etc/hosts:
  • Comment out the appropriate line:
    e.g. # ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
  • Confirm the appearance of the following line:
  127.0.0.1 localhost.localdomain localhost
• On Windows, verify that:
  • The Secondary Logon Service is running. You can check under Administrative Tools > Services.
  • The account has Log on as a service permissions. You can check under Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment.

Note: All host names required for the installation should be fully-qualified and resolvable by DNS.

Installing a Manager

Contact Signiant Customer Support to obtain the installer.

To install a Manager:

Linux

1. Extract the tar.gz file contents:
   tar -zxvf <filename>
2. Navigate to the extracted directory and run the installer:
   ./install.sh
3. Follow the onscreen instructions and enter the required information when prompted.

Windows

1. Download and run the .exe file to extract the contents into a temporary folder and launch the Signiant installer.
2. Follow the onscreen instructions and enter the required information when prompted.

Note: If you are prompted to restart your computer during installation, finish installing the Manager software before restarting.

Installation Options

Installation Key Options

Installation keys allow Signiant administrators to control the number of Agents a user can install. The Certificate Authority generates these keys, which are valid for a specific period of time.

Choose to require installation keys for Agent installation or to allow Agent installation without an installation key. By default, Agent installation does not require an installation key.

Installation Mode Options

Rapid Basic Installation (RBI) automatically uses Signiant configuration options to get started quickly with Signiant Agents. It also includes keyless Agent installation. This mode of installation is appropriate in production environments where the advanced security functions of the Signiant software are not required, as well as in test environments.

Choose to enable or disable Rapid Basic Installation Mode. RBI is enabled by default.

Default User Options

• Use system on Windows and root on Linux: Use the specified values as the default user on Windows and Linux.
• Specify other values for the default users: Allows users to specify their own values for Windows and Linux default user and password, as well as for the Windows domain.

Default User IDs

These options appear if you select Specify other values for the default users.

• Default Userid (Linux/Windows): This user ID must exist or be resolvable on the Agent. It is not created during installation.
• Windows Domain: This value is used to qualify user IDs and grants for Windows hosts.
• Windows Userid Password: The password for the specified default user on Windows.
• Verify Windows Userid Password: Confirm the password for the specified default user on Windows.

For custom setups only:

• Linux: The default directory used by Linux Agents when a directory is not explicitly specified in a workflow component.
• Windows: The default directory used by Windows Agents when a directory is not explicitly specified in a workflow component.
• Administrator #: Specify up to five Signiant administrator userIDs for users allowed to perform administrative tasks on the local Agent.
• Group Name: The group to be used for group privileges on the Manager host. The installation creates this group if it does not already exist.

Port Number Options

You must assign the AgentPort, RulesServerPort, and SchedulerPort to set up Signiant services on the Manager host. Enter the port number on which the specified service will be running.

Note: Signiant requires that ports 80 and 443 be available for Manager/Agent communication. If another application on your system is using these ports, the application will warn you to make the port(s) available and re-run the installer.

Certificate Authority Setup Parameters

• Organization Name
• Locality (City)
• State/Province
• Country Code: The Country Code is in X.509 standard, for example US for United States, CA for Canada.
• Organizational Unit: A division or department of your organization.
• CA Common Name: Common name for the Certificate Authority. This can be any combination of alphanumeric characters, symbols, and spaces. For Agents communicating with Agents in other organizations, this field must be unique across organizations. To ensure unique names, the fully qualified domain name of the host is appended by default.
• Admin Password: The password used to log into the Signiant Manager.
• CA Passphrase: The passphrase is used to unlock the Certificate Authority key. It must be at least seven characters long. Since the CA password phrase protects the actual CA, it should be long and complex, since it seldom (probably never) changes. Record your passphrase in a safe place.
  Note: If you perform a standard install, you will not be required to enter a CA passphrase. The passphrase is automatically set to match the admin user password.
• CA AdminPassphrase: This frequently-used passphrase is used to perform CA administrative functions. It must be at least seven characters long. Record your passphrase in a safe place.

Logging into the Manager

Once you install the Manager, you can log into it using the URL provided by your Signiant administrator.

The Manager URL should be in the following format: https://<Manager_address>/signiant

The <Manager_address> is the fully qualified hostname of the Manager.

Adding License Keys

To use the Signiant software and any additional features or applications purchased, you must add their licenses to your Manager. The Licenses page displays a list of the features for which you have purchased a license, as well as the associated license key, its expiry date, the date it was added, its status (Active or Expired), and the licensed Agent count for the feature.

To add a license key to the product:

1. In your Manager, navigate to Administration > Manager > Licenses.
2. Click Add.
3. Enter the license key(s), separating multiple keys with a space or a line break.

Configuring E-Mail Notifications

By default, Manager notifications are sent from transmgr@<manager_host_name>.

Although most mail servers will have no problem accepting mail from this address, some email server configurations will only accept a valid email address that exists in the domain. In these systems, failure to update the email address of the sender will result in disruptions to email notification delivery. In this event, errors recorded in the mail server event log will indicate mail being rejected from the Signiant Manager server.

To configure email properties:

1. On the Administration > Manager > Email Notification page, click the Edit tab.
2. Specify the following:
   • Mail Server
   • Mail Server Port: The default value is 25.
   • Mail Server Connection Mode
   • Mail Server Connection Timeout (seconds): This is a mandatory field with a minimum value of 10 seconds and a maximum value of 600 seconds.
   • Email Address of Sender
   • Name of Sender
3. If applicable, select Enable server authentication and specify a Username and Password.
4. Click OK to save and exit, or Apply to save and keep the dialog open.

Sending a Test Email

To test the email notification feature:

1. On the Administration > Manager > Email Notification page, click the Send a Test Email tab.
2. Enter a recipient email address.
3. Enable SMTP Loggingto retrieve and display SMTP logging messages for this test email in the Mail Log panel. These messages are not saved to a log file.
4. Click Test.
5. Click OK to save and exit, or Apply to save and keep the dialog open.
6. Log into the account for the test email address to verify that the test email was received.

Updating Maintenance and Backup Jobs

On a fresh install, Signiant creates default log maintenance and Manager backup jobs, with a default schedule and preferences. You can modify these jobs to suit your own scheduling needs and add an email address for notification purposes, in case of job failure.

For the backup job, you must first install an Agent to which to assign the backup.

Before deleting old maintenance and backup jobs, verify that they were properly migrated to the new versions.

To verify the migration, navigate to Jobs > Report > Job Groups and comparing the old jobs to the migrated versions.

Note: Do not un-suspend the old jobs, as they will interfere with the new backup/maintenance jobs.

Copying an Administrative User

Signiant recommends that you have at least two accounts with administrative access, in case one account is locked out or a password is forgotten.

To create a second administrative account:

1. In your Manager, navigate to Administration > Users > List.
2. In the user list, select User, Admin and click Copy.
3. Fill in new information for the user and click OK.

Configuring Third Party Certificate Usage

On some browsers, you may get a warning every time you log into the Signiant Manager. To avoid receiving this message, you can obtain a third-party certificate for your JBoss server through Signiant.

Upgrading a Manager

Upgrading ensures you have the latest features and updates to the Signiant Manager+Agents software, while keeping your existing configuration.

A software upgrade stops all Signiant processes, including any scheduled jobs.

Manager upgrade times vary greatly depending on the system being upgraded, and there may be little indication of progress during the upgrade. Make sure that you perform your upgrade at a time that will ensure the least disruption to your system. Before upgrading your Manager, ensure it is backed up.

Note: Make sure you are not running System Health when performing an upgrade.

To upgrade a Manager:

Linux

1. Download the compressed tar.gz file from the Manager+Agents portal to a temporary location on your Linux server.
2. Extract the tar.gz file contents:
   tar -zxvf <filename>
   e.g. tar -zxvf DTM_LRH6_64_12.0.100.SIGNIANT.tar.gz
3. Navigate to the extracted directory and enter install.sh.
4. Follow the instructions on each screen, and input the required information.
   Note: On the Signiant Administrative Password screen, the existing Manager admin password will be reset to what you enter.
5. Verify that a backup job exists and still works. Ensuring that the backup job exists and works in your upgraded Manager makes restoring from a backup possible.
   For information on running the backup job, see Configuring Manager Backup.

Windows

1. Run the downloaded .exe file. This will extract the contents into a temporary folder and will automatically launch the Signiant installer.
2. Follow the instructions on each screen, and input the required information.
   Note: On the Signiant Administrative Password screen, the existing Manager admin password will be reset to what you enter.
3. Verify that a backup job exists and still works.
   For information on running the backup job, see Configuring Manager Backup.

Uninstalling a Manager

To uninstall the Manager:

Linux

1. In your terminal, run the uninstall command: <signiant_install_directory>/bin/siguninstall
2. Follow the onscreen prompts to remove the software.
3. When prompted to remove the database and all users and groups, choose Y. If you choose N, you can remove the database and all users and groups manually at a later point.

Windows

1. Navigate to Control Panel > Programs > Programs and Features.
2. Locate the Signiant software and click Uninstall.

Manually Removing the Database

If you choose not to remove the database when uninstalling the Manager components on Linux, you can do so manually in your terminal.

To manually remove the database, run rm -fR <install_directory > /db.

Manually Removing Users and Groups

If you choose not to remove users and groups when uninstalling the Manager components on Linux, you can do so manually in your terminal.

To manually remove the users, run userdel [-r] <userid>.
Note: The user's home directory will be removed along with the user's mail spool.

To manually remove groups, run groupdel <groupid>.

Enabling and Disabling SSL V3

On new installations, SSL V3 communication is disabled by default. For any upgraded installations, the SSL V3 status is not impacted.

Use the sslEnableDisable.pl script to manage the enabling and disabling of SSL V3 communication. This script is located in <signiantHome>/bin.

The parameter options for sslEnableDisable.pl are: enableSSLv3 or disableSSLv3 (e.g. sslEnableDisable.pl disableSSLv3).

Note: SSL 1.0, 1.1, and 1.2 are always supported.

If SSL V3 is disabled on your Signiant Manager and you have written Perl scripts that use the Net::SSL Perl module for HTTPS communication, you must modify your Perl script to use IO::Socket::SSL module.

If you have the following line in your Perl script: use Net::SSL:

1. Remove use Net::SSL.
2. Insert the following:

if (eval {require IO::Socket::SSL;1})
{
     IO::Socket::SSL- > import();

     IO::Socket::SSL::set_defaults(SSL_verify_mode = >  SSL_VERIFY_NONE);
}
else
{
     require Net::SSL;
     Net::SSL- > import();
}

If the SSL verify mode needs to verify the server certificate, insert the following:

if (eval {require IO::Socket::SSL;1})
{
     IO::Socket::SSL- > import();

     my $caCertString = '<PEM encoded CA certificate string > ';
     require IO::Socket::SSL::Utils;
     IO::Socket::SSL::Utils- > import('PEM_string2cert');
     my $caCertHandle = PEM_string2cert($caCertString);
     IO::Socket::SSL::set_defaults(
                 SSL_verify_mode = >  SSL_VERIFY_PEER,
                 SSL_ca = >  [$caCertHandle]
                 );
}
else
{
     require Net::SSL;
     Net::SSL- > import();
}