Secure Delivery Center Installation Guide

1. Installation Overview

Secure Delivery Center (SDC) is a software distribution manager that assists administrators in providing software to various groups in their organization with little to no effort by end users. This guide provides instructions on installing the various components of SDC, which are listed below.

  • Server (Delivery Hub) Software: The SDC delivery hub software controls all aspects of software delivery and software pack installation. The delivery hub software must be running to install the following software packs.
  • Eclipse Discovery Software Pack: The Eclipse Discovery software pack installer includes all Eclipse-based components needed to create end-user installers for MyEclipse or Eclipse software.
  • Java 1.6 Software Pack: Includes Java run-times necessary for creating end-user installers for MyEclipse software. This pack is not necessary for distributing Eclipse Standard software.
  • MyEclipse Software Pack: The MyEclipse software version you want to distribute to your end users. This is not the same as an installer used when running software outside the context of SDC. Instead, this pack installs the components necessary for creating end-user installers for the software.
  • Certified Software Pack: A collection of some of the most popular Eclipse plugins available. Genuitec certifies the integrity of the downloads and makes them all available for use in SDC in a single pack.
  • Database: A database stores server, or hub, history information. A database is included in the SDC installation, or you can connect to an existing external database.
  • Admin Console: The Admin Console software is installed on administrators' desktops for managing software distribution. The Admin Console installer is generated when you install the SDC server software.
  • Signing Agent: If any end users are running either OS X Mountain Lion or Windows 8, you must digitally sign installers that will run on those systems. SDC includes a signing agent that automatically signs installers with your digital signature. Signing agent installation is not required if no end users are running either of these operating systems or if the operating systems are configured to allow running unsigned installers.

When you install SDC, you install the server (delivery hub) software and the software packs onto the same machine. Software packs are not stand-alone, installable software, rather they contain the pieces required to build an end-user installer based on packages you create using the Admin Console. Administrators install the Admin Console onto their desktops to control and manage software delivery. The Admin Console is available for installation from the Admin page of a portal web page.

SDC also requires a database to be installed for storing alerts, metrics, and errors. The data stored is essentially a history of software distribution. When you install SDC, you can either connect to an existing database, or you can use the database bundled with SDC.

 

1.1 System Requirements

Delivery Hub Hardware

  • Linux server with 1.5 GB memory (Linux is preferred, but Windows and Mac are also supported)
  • 20-40 GB free disk space for common installation
  • Intranet DNS hostname assigned for server(s)

Client Hardware

  • Windows, Linux, or Mac OS X
  • No minimum requirements - dependent on tool stack being delivered

Software

  • No additional software required
  • Compatible with SMS systems
  • Optional: external database, either Oracle or MySQL; a database is included with installation, so no additional database is required.

 

2. Installing The Delivery Hub Software

  1. Double-click the SDC installer file.

    Note: If on Linux, you might need to make the .run file executable via chmod u+x server-installer.run (Replace server-installer.run with the name you have downloaded the SDC software install to.)

  2. Click Next to view the license agreement.
  3. Select the I Accept... checkbox, and click Next.
  4. Choose server options. First, you can install SDC as a system service, which requires admin rights, or you can install as software into your user account.

    Note: When installing on a Mac, the system service option is not supported; therefore, the option is unavailable.

    Second, select the database you want to use, either the database embedded within SDC or an existing external database. If you are using an external database, select it from the Use External Database drop-down. You can choose from either Oracle or MySQL.

    5. Selecting server options
  5. Click Next. If you are using an external database, enter your database information as described below. Otherwise, skip to the following step.

    Note: In MySQL, the user name and password you enter must have permissions to create tables in the given schema.

    6. Entering external database information
  6. Specify the installation and data folders. The default paths place the SDC installation folder at the same level as the data files folder. Click Next.
    7. Setting installation and data folders
  7. Enter the username, name, and password of the initial administrator, and click Next.
  8. Enter the hostname or IP address and port at which you want to receive incoming requests. Click Next.

    Note: If you have a non-static IP address, you should use the computer's hostname rather than the IP address. This hostname will be part of the SDC web portal URL, so it will be visible to your users. We strongly recommend using a fully qualified domain name so users roaming onto a VPN can still connect to the server.

    9. Entering hostname information
  9. Click Next to install the server. When installation is complete, click Finish. The SDC software starts automatically.
    10. Successful installation

    By default, the Display the Secure Delivery Center First Steps Help Page checkbox is selected. This opens the login page to the portal. Log in using the administrator login specified during server installation. Once logged in, a help page opens giving you a list of what to install next, and a link to the Admin Console installer. You should bookmark this help page for future reference. For those installing silently, the link to the help page is in the following format: http://<hostname>:<port>/admin/firststeps/.

 

2.1 Starting the Delivery Hub Software

When you first install the delivery hub software, it starts automatically. Your platform and how you chose to install the software determines how you start and stop the delivery hub software thereafter. To see system progress and to verify the hub software started properly, you can view the log by navigating to the installation folder for Secure Delivery Center, and then \Data Files\logs\server-details-0.log.

Windows

If you installed on Windows as a system service, you start and stop the hub software through the Services control panel.

If you installed into a user account, start the hub software by running deliverycenterserver.exe in the C:\Users\[username]\AppData\Local\Secure Delivery Center\Server\server folder. To stop running the hub software on Windows when installed into a user account, end the process on the Processes tab of the Task Manager.

Linux

If you installed as a service, start/stop the hub software using the following command:

service genuitec-sdc <start/stop>

If your Linux version does not support services, use the following command:

/etc/init.d/genuitec-sdc <start/stop/status>

You can also use your desktop's activity monitor to stop the server process.

If you installed into a user account, start the hub software by running deliverycenterserver in the [installation folder]\Server\server folder. Use your desktop's activity monitor to stop the server process.

Mac

Installing as a service on Mac is not supported. To start the hub software, double-click the deliveryCenterServer file in the applications list. Stop running the hub software by right-clicking the icon on the Dock to quit the process.

 

3. Installing Software Packs

To use SDC for on-demand delivery to Eclipse installations, you are not required to install software packs. However, to simplify marketplace catalog creation, you can install a certified poplular software pack, which installs onto the delivery hub machine many popular software add ons. If you are installing a certified software pack, continue to the next section. Otherwise, you can skip to Installing the Admin Console.

To use SDC to distribute secure IDEs to your end users, you must install software packs. The software packs contain the components necessary for creating installers based on packages you create in the Admin Console. The packs required depend on the software you are delivering.

 

3.1 Installing a Certified Software Pack

Installing a certified software pack is useful for both secure IDEs and on demand delivery. To install a Certified Software pack, you must have the SDC delivery hub software running.

  1. Double-click the Certified Software pack installer file.
  2. Click Next view the license agreement.
  3. Select the I Accept... checkbox, and click Next.
    4. Certified software pack installation
  4. Click Finish to complete installation.

Note: If you are using SDC for only on-demand delivery to existing Eclipse installations, skip to Installing the Admin Console.

 

3.2 Installing the Eclipse Discovery Pack

To install Eclipse Discovery, you must have the SDC delivery hub software running. You can install one or more versions of Eclipse Discovery. If installing version 9.x of MyEclipse software, you need to install Eclipse Discovery 3.6.1. For version 10.x of MyEclipse software, you need to install Eclipse Discovery 3.7.0.

  1. Double-click the Eclipse Discovery pack installer file.
  2. Click Next to view the license agreement.
  3. Select the I Accept... checkbox, and click Next.
    4. Eclipse Discovery pack installation
  4. Click Finish to complete installation.

 

3.3 Installing the Java 1.6 Pack

To install Java 1.6, you must have the SDC delivery hub software running. Installing the Java 1.6 software pack is not required for distributing Eclipse Standard software.

  1. Double-click the Java pack installer file.
  2. Click Next to view the license agreement.
  3. Select the I Accept... checkbox, and click Next.
    4. Java pack installation
  4. Click Finish to complete installation.

 

3.4 Installing the MyEclipse Software Pack

To install a MyEclipse software pack, you must have the SDC delivery hub software running.

  1. Double-click the MyEclipse pack installer file.
  2. Click Next view the license agreement.
  3. Select the I Accept... checkbox, and click Next.
    4. MyEclipse software pack installation
  4. Click Finish to complete installation.

 

4. Installing the Admin Console

The initial administrator must install and run the Admin Console, and then add all admin usernames and passwords to the system so other admins can access the Admin Console installer. The Admin Console installers are available on the portal web page.

To install the Admin Console, you must have the SDC delivery hub software running.

  1. From the admin desktop, access the portal web page at http://<your hostname>:<port>/. The port number in the URL needs to match the port number you entered when installing the SDC delivery hub software.
  2. Click the Login tab, enter the username and password you specified during SDC delivery hub installation, and click the Administration tab.
  3. In the Admin Console section, click the platform to which you are installing. This downloads the Admin Console installer file.
    4. Selecting the Admin Console installer
  4. Double-click the installer file.
  5. Click Next view the license agreement.
  6. Select the I Accept... checkbox, and click Next.
  7. Either accept the default installation folder, or change the folder, and click Next.
    8. Specifying the installation folder for Admin Console
  8. Click Finish to complete installation.
  9. Log into the Admin Console.
  10. Click Users under Administration in the Admin Console navigation. Enter all admin usernames and passwords. For more information, see Managing User Accounts in the Administration Guide.

After adding administrator accounts, each admin can access the web portal page and install Admin Console following steps 1-8.

 

5. Installing Signing Agents for Digital Signatures

OS X Mountain Lion and Windows 8 operating systems require applications downloaded from the Internet to be signed. Therefore, the SDC installers generated for users on those systems must be signed. A Signing Agent is included with SDC to automatically sign package installers on Windows and OS X as required.

Note: Digital signatures on installers are required only for OS X Mountain Lion and Windows 8. If end users are not running on either of these operating systems or if the operating systems are configured to allow running unsigned installers, you are not required to install signing agents.

The following elements must be in place for digital signing to occur using SDC:

  • If you're signing both OS X and Windows installers, a machine running each operating system must be available as a signing "helper". These machines must be able to connect to the SDC delivery hub. It is not necessary for these machines to be dedicated to this task.
  • Obtain and install a digital signing certificate for each operating system from a Certificate Authority. Install the signing certificate on the helper machine of the respective operating system.
  • For Windows, you must have the Windows signing tool available, which is part of the Windows SDK (http://go.microsoft.com/fwlink/?linkid=84091). For OS X, you must have the Xcode signing tool (https://itunes.apple.com/us/app/xcode/id497799835?mt=12). These signing tools must be installed on the "helper" machine of the respective operating system.
  • Install the SDC signing agent on the helper machine(s) as described in the steps below.
  • Configure the certificate in the Admin Console. See Configuring a Signing Certificate for Windows or OS X in the Administration Guide.

    Installing a Signing Agent

  1. From a signing helper machine, access the portal web page at http://<your hostname>:<port>/.
  2. Click the Login tab, enter an administrator username and password, and click the Administration tab.
  3. In the Admin Console section, click the signing agent link for the platform to which you are installing. This downloads the signing agent installer file.
    4. Selecting the signing agent installer
  4. Double-click the installer file.
  5. Click Next view the license agreement.
  6. Select the I Accept... checkbox, and click Next.
  7. Either accept the default installation folder, or change the folder, and click Next.
    8. Specifying the installation folder for the signing agent
  8. Click Finish to complete installation. By default, the signing service is set to start automatically when a user logs onto the helper machine. The signing agent must be running for package installers to be signed.

Configuring the Signing Agent

When you first open the signing agent, you must specify the URL to the SDC delivery hub. After the hub locaion is specified, the agent automatically searches the SDC hub machine for installers of the same operating system as its host machine. When the agent then signs unsigned installers.

  1. With the signing agent open, click Preferences.
    2. Opening preferences
  2. Enter your SDC delivery hub machine URL in the format http://<hostname>:port, and click the Add icon .
    3. Setting the delivery hub URL


6. Installing on a Linux Server in Unattended Mode

In some Linux installations, you are unable to click through an installer because the server isn't running a graphical user interface. In this case, you must use the unattended installation mode to run installers. To activate the unattended mode, run the installer file from the command line with the following arguments:

--unattended <full path to your response file>

For example:

delivery-center-server-4.2.0-installer-linux.run --unattended /home/root/unattended.properties

The unattended.properties file contains responses to questions that would normally be asked in the installer. Below is a sample of a server unattended installer response file.

Note: The software pack installers only require the result.file property in the response file.

server.dir=/home/user/sdc/server
server.data.dir=/home/user/sdc/data
result.file=/home/user/sdc.result.txt
admin.fullname=Administrator
admin.password=abc123
admin.username=admin
database.engine=BUNDLED
server.hostname=sdc.mydomain.com
server.install.as.service=false
server.port=1305

If you fail to include a property or configure a property improperly, the installer indicates what the offending property is and the value it is expecting.

Property Data type Required Description
admin.fullname String Yes the full name of the initial administrator
admin.password String Yes the password of the initial administrator
admin.username String Yes the user name of the initial administrator
database.engine “BUNDLED” or “INSTALLED” Yes tells the installer if the bundled database should be used or if a previously installed database should be used
database.hostname String Required if database.engine=INSTALLED is specified the hostname or IP address of the database host
database.password String Required if database.engine=INSTALLED is specified the password the server should use to access the database
database.port integer Required if database.engine=INSTALLED is specified the port of the database server to which the server should connect
database.schema String Required if database.engine=INSTALLED is specified the schema in the database to which the server should connect
database.type “MYSQL”, “ORACLE”, or “POSTGRESQL” Required if database.engine=INSTALLED is specified the type of database to which the server connects
database.username String Required if database.engine=INSTALLED is specified the user name the server should use to access the database
database.url String Required if database.engine=INSTALLED is specified the jdbc URL used to connect to the database/schema
result.file path Yes a path to the installation result file which will be created and populated with the results of the install
server.dir path Yes a path to the location where the server should be installed
server.data.dir path Yes a path to the location where the data files should be installed
server.hostname String Yes the hostname or IP address of the SDC server
server.install.as.service “true” or “false” yes indicates if the server should be installed as a service (requires root access) or as a user application
server.port integer yes the port the server should listen to to serve requests