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.
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.
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.)
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.
Note: In MySQL, the user name and password you enter must have permissions to create tables in the given schema.
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.
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/.
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.
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.
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:
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.
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.
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.
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.
Note: If you are using SDC for only on-demand delivery to existing Eclipse installations, skip to Installing the Admin Console.
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.
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.
To install a MyEclipse software pack, you must have the SDC delivery hub software running.
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.
After adding administrator accounts, each admin can access the web portal page and install Admin Console following steps 1-8.
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:
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.
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>
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.
|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|