Secure Messaging Server Console... 2 Upgrading your PEN Server Console:... 2 Server Console Installation Guide... 2 Prerequisites:... 2 General preparation:... 2 Installing the Server Console... 2 Activating the Console... 3 Creating a Virtual Private Server (VPS)... 3 POST VPS Creation... 5 Installing Memcached and configuring the VPS... 5 Creating a new Secure Messaging Platform (customer deployment)... 6 Secure Messaging Platform: Server Console Admin User Guide January 2012 PAGE 1 of 6
To install the Secure Messaging Platform on your own server, please download and review the requirements and procedures described in the Installation Guide. The installation Guide for the email2 PEN Server Console can be found here: Server Console Installation Package: email2penserversetup-[04/13/2011]-v2.0.4119.exe Log in to your server. Click on the email2penserversetup.exe link above. The installer will remove the previous version and install the latest version. No configuration files will be removed during this process. Follow the online instructions to complete the installation. Application Server: Windows Server 2008 R2 with IIS 7..Net Framework 4.0. Shared Management Objects installed. Install Memcached. Data Server: Windows Server 2008 R2. SQL Server 2008 / SQL Server 2008 R2. The Data Server can be deployed in the same physical machine or be reachable in the same network by the Application Server. It is recommended that a new administrative level user is created in the Application Server OS and install the Server Console under that account. Whether it is a dedicated Windows user or other, in this document we refer to this Windows user as Admin. With Windows Server 2008, confirm that IIS 6 Metabase Compatibility is enabled under Roles / Web Server / Management Tools. The Server Console needs this to create virtual directories. With IIS 7, please make sure the Static Content is enabled under Roles / Web Server / Common HTTP Features. If this is not enabled, images and CSS will not be available. Download the latest version of the Installation Package. Download and install the prerequisites. Download and install the Server Console. PAGE 2 of 6
To begin using the Server Console, you must complete the Activation process. Please follow the steps below to complete this process: 1. Start the Server Console. 2. Enter in your personal information into the Server Console page. Note: Security Code & Master Password boxes are greyed out. They will only become active once you have submitted your personal information for Activation. 3. Click Start Activation. 4. Click OK. Your personal information is now greyed out, and the Security Code & Master Password boxes are available. A message has been sent and a representative will contact you shortly with your Security Code. You may close the console and re-open it at any time to return to this state. 5. Once you have received your Security Code, enter it into the Server Console. 6. Enter a Master Password. This is the password you will use to access the Server Console. 7. Click Activate to complete the activation. 8. The Server Console is now activated. Initial Configuration and Updates: Before you can move on to create a Virtual Private Server (VPS), you need to specify the root folder where all Virtual Servers are located. This is a default configuration that can be overwritten when creating a Virtual Server, but it is the recommended folder hierarchy for the entire system. This step is required only the first time the Server Console runs. Each time that you start a new session with the Server Console, there could be application updates available and the user is offered the option to download them immediately. These updates (VPS install package and service packs) are not automatically deployed to a Virtual Server. They are only available to the Admin to be applied later on. There are two types of updates: o o VPS Install Package. Service Pack. In order to create a new VPS, start the Server Console, and follow these steps: Note: You will need to run the Server Console with Administrative privileges 1. The Login page appears. Enter your Master Password. 2. If there are new updates for the Server installation packages, you may be prompted to download them. It is recommended that you complete this action at this time. These updates will not be deployed to a VPS until you explicitly use the option to upgrade (this operation only makes the service packs available in the local disk). Once the downloads have completed, click OK. 3. In the main window of the Server Console, click Add VPS at the top. This will initiate the VPS Creation Wizard. Click Next. 4. VPS Planning and Preparation. This page provides a basic description of the items and tasks you will need to prepare or plan for in order to successfully create a VPS. Once you have prepared all of the items and tasks, click Next. 5. VPS Application Settings. This page is where you will set all of the settings for the Application. Specific information is provided below: PAGE 3 of 6
a. VPS Name: This is the display name for the new VPS you are creating that can contain multiple customer deployment all sharing the same database schema. This is for internal purposes only and is not visible to the customer. b. Code: In order to create a new VPS, a new customer deployment must be created located in the VPS. This code is used as the default prefix for all folders related to this VPS. c. Root Folder: Specify the root folder in the file system that will host all customer deployments in this VPS. d. Admin User ID & Password: These are the credentials you will use to log into the Web Admin Console to gain access to the customer Secure Messaging Platform. e. IIS Website: This option allows you to specify an existing IIS Website, or to create a new IIS Website. In the trial version, the option to create a new IIS Website is disabled. Choose an existing IIS Website for this option. f. Server URL: Please specify the Server URL that the website will have. This is also where you select whether the website will use SSL or not (http:// vs https://). Please make sure that the bindings for the website (i.e., the domain name associated to the website) is properly configured. The Console will detect the default binding associated to the website and populate this field automatically. 6. Select SQL Server Database for this instance. This page is where you select the SQL Server instance where the database schema for this VPS will be created. a. SQL Server Name: Enter the name of the SQL Server. You can either enter the name or IP address of the SQL Server you want to use or use the dialog to search for all available SQL Servers that the Application Server has access to in the local network. b. Database Schema: You can either choose an existing database schema in the previously selected SQL Server instance or allow the Server Console to automatically create a new one. If you choose the option to create a new database schema, the Server Console will automatically populate the name. Also, when this option is used the database user and password are automatically created. If you choose an existing database schema you must make sure that it is empty as all objects in it will be overridden. This option is provided so you have better control on the definition and security of the database schema. c. Security for Existing db Schema: This option is available only when you choose an existing database schema. Click on the link to open the dialog and select the appropriate database login. The selected SQL Server login must have dbowner privileges over the database schema selected above. d. New Database Schema Details: If you are creating a new database schema, you must specify where the Server Console should store the corresponding data files. There are three options available: If the SQL Server instance is hosted in the same server that the Application Server, you must specify the local path in this server. The Console will populate this field with a default value. If the SQL Server instance is available in a remote server, you need to specify the Remote Folder. In this case, you need to make sure that the folder exists in the remote location as the Server Console will not be able to create it automatically. Finally, you can also use the same location as the master database, which works for both local and remote SQL Server options. 7. Login to master SQL Server Database. Follow the instructions on the page to enter the SQL Server User Name and Password that are required to create a new database. This is either the Integrated Authentication with the current Windows user or a SQL Server login name. In both cases, the SQL Server user needs to have the appropriate privileges to create a new database and execute the installation scripts. The wizard provides an option to test the connection to confirm that it has the correct credentials. Click OK when complete. 8. Summary of Installation. This page provides a summary of all of the settings and operations that will be executed to complete the creation of the VPS. Please confirm the settings and then click Execute. Once the VPS creation completes, you should receive a confirmation message that it was created successfully. NOTE: If you receive an error, please contact your reseller. NOTE: You may need to restart the Server Console to see the newly created VPS. PAGE 4 of 6
Identify the Application Pool s user used for the IIS website and grant permissions to these folders: <Root Folder>\docs <LocalAppDataFolder>\email2\penSeeds C:\email2\qFolder NOTE: <Root Folder> is the folder selected in the steps above NOTE: <LocalAppDataFolder> is the local application data folder for the current Windows user. For example, for the user email2 in Windows Server 2008 this corresponds to C:\Users\email2\AppData\Local\email2\penSeeds Configure Memcached for this VPS and edit the web.config accordingly (see below). Create the appropriate bindings for the website / domain selected above. The domain name specified above is the base URL for all Secure Messaging Platforms (customers) created in this VPS. You may decide to reuse the same website for multiple VPS or have a new website with its own domain name for each VPS. This configuration must be completed manually. Make sure that the IIS Application Pool used by the selected website is configured to use the.net Framework v2.0 and using the Classic managed pipeline mode when working under Windows Server 2008. SSL Certificate. If you specified a secure domain (mandatory for production deployments), you need to properly configure the website and install the corresponding SSL certificate for the domain you specified. 1. Download the memcached package. 2. Unzip this into a folder of your choice (e.g., C:\memcached ). 3. In the Command Prompt create the following service: sc create <service_name> binpath= "<memcached_path> -d runservice -p <port_number> -m <memory_allocated>" start= auto DisplayName= "<display_name>" example: sc create mcemail2 binpath= "C:\memcached\memcached.exe -d runservice -p 50000 -m 512" start= auto DisplayName= "MemCached 20002" 4. Configure your VPS to use this memcached instance by adding the following keys to your web.config folder found in the VPS www folder: <configuration> <appsettings> <add key= e2_cacheip value= <memcached_server_ip> /> <add key= e2_cacheport value= <memcached_service_port> /> </appsettings> </configuration> NOTE: memcached_server_ip should be 127.0.0.1 in single web server scenarios. NOTE: memcached_service_port is the port number you used when creating the service. PAGE 5 of 6
To create a new branded Secure Messaging Platform for a customer, select a VPS and click Add PEN. After selecting Add PEN, you will see a screen requesting information for creating the new customer: Code: This is where you specify the code for the URL of the Secure Messaging Platform e.g. https://[website-name]/[code]. This information is required. Name: This is the full display name of the Secure Messaging Platform that will appear for the customer in all Notification Messages, and within the various end user applications. This information is required. Admin UI User: This is the User Name, Name, and Password that is automatically created for the group administrator for the Web Admin Console access. The Username defaults to code_admin. These fields are required. Admin Email: This is where you specify the Admin email account for the Secure Messaging Platform. This user is autoprovisioned, and is the address that all Notification Messages will be sent from. It is recommended that this be set to a generic, Customer Service address (for example, support@your_organization.com). These fields are required. Customer Branding: This is where you can specify a custom banner and icons for the Secure Messaging Platform. If no banner or icons are specified, generic images will automatically be assigned. These fields are optional. Registration Information: This is where the customer information for the Secure Messaging Platform can be entered. These fields are optional. Once you have entered all of the required information, click Create Customer. Please wait for the process to complete. Once complete, you will receive a confirmation message that the Secure Messaging Platform was created successfully. NOTE: If you receive an error, please contact your reseller. NOTE: It is strongly recommended that you confirm that the Secure Messaging Platform is fully operational by expanding the VPS, and clicking the Secure Webmail link for the newly created Secure Messaging Platform. PAGE 6 of 6