Page Comparison

Once the installer has been launched you are presented with a menu of options.  We will focus on configuring a server for the first time in this guide, other options are discussed in Other uses of the Swift MEAP Installer.

To configure a new server:

1. When the installer is opened, the first option presented in the list is to deploy a new mobile server.  Click to select and you will be prompted for the Tomcat path. 
   
   1. Choose browse, and navigate to the home directory for Tomcat. This is the directory which contains the bin, lib, webapps, etc subdirectories. Choose open to confirm the path.  If you have run the installer before, it will remember your last choice.
   2. Below the window displaying the path, there is a 'Tomcat Version' selection box.  Ensure the correct version is selected in the dropdown list
   3. Select Next to continue.

2. The next screen will ask you for your war file.

   1. This file should have been received from iEnterprises. Its name will be similar to MEXX9.0.0.war.
   2. Navigate to its path, and click Open. The installer will extract your war file.
   3. Click Next to move to the next step.
      
      

3. Enter your MySQL details.

   1. The simplest MySQL setup is on the local server (localhost, port 3306), using the root MySQL user and password.  Any user which can create databases can be used, but root is the most common.
   2. Once you've entered in the server, port, username and password, click the blue + to create a new schema.
   3. The schema's name should be all one word. For example, you might choose the schema name: mobileserver
   4. Your new schema name should now appear in the line next to Schemas.
   5. Click Test Connection to ensure that the mysql setup is working as intended. If it is correct, the Next button will now be clickable.
   6. Click Next to continue.
      
      

4. Confirm MySQL / schema details.  In the next screen, you may choose to add an additional user to MySQL in order to not use the root MySQL user for continued access to the Swift MEAP server's database.

   1. Click the button next to the user list field to create a new user for your Swift MEAP installation, if desired.
   2. Check that correct user is displayed in the User List, confirm password and Schema.  You may need to click on the 'Set Privilege' button next to the schema list if you have changed user and they do not have permission to access the schema.
   3. Choose Test Connection to proceed.
   4. The next button will be clickable if the connection test succeeded.
   5. Click next to continue.

    

5. You will be presented with a screen which will show the database scripts being run that create the database schema.  Several tables will be set up, this can take several minutes to complete.

   1. Any errors will be displayed and will also be added to the logs.
   2. There is an 'Edit System Keys' button at the top of the screen if you wish to change settings before deployment, but these can be changed in the Admin Console later.  It is recommended that these settings are not altered, unless you were specifically instructed to do so.
   3. Assuming there are no errors, click next to proceed.
      
      
6. Configure the server details.  The next screen allows you to configure the logging details, ports and server details:
   

   1. Set the path for the Swift MEAP log files that you created earlier in the Linux or Windows installation section of the document. 

      1. The default logging level should be left at "info".  It is possible to change it later in the Swift MEAP™ admin console on the fly.  Please see How to change the server logging level for more information on changing the logging.
   2. The Mobile Server Name you enter here will be the context in the URL that is accessed later. It is often advisable to make this name the same as the database schema name. For example: mobileserver
   3. Configure Ports.  You can choose to run the administrative console and the server servlets on different ports. For more information see Before You Get Started.
      1. Single port - basic installation:  For a basic installation, using the default Tomcat port 8080, you do not need to select anything.
      2. Split port - advanced installation:  For an installation using two ports, select the checkmark next to 'Run Mobile Server admin console and Service Servlets on two different ports to increase security'.  This will prompt you for additional information:
         
         1. Admin console port:  This is the port that an administrator will use to access the admin console.  It is the URL they will enter in a browser to access.  For example: http://your.company.com:8085/mobileserver
         2. Service port:  This is the port that all exernal devices connect over and will need to be open.  In the example here, we will define port 8086.  All devices will therefore need to be able to connect to this port.  The 'Used Ports' section will display ports that you already have in used, so a duplicate is not selected.
         3. URIEncoding:  Usually UTF-8, if you should change this, you will be advised to do so, otherwise, leave the default value.
         4. Service URL:  You need to confirm the full URL that devices will connect to.  This should include the service port / mobile name context, including whether it is http or https.  If this is set incorrectly, your devices will not operate and you will see isssues in the admin console completing certain operations.  Please set this carefully, in the format:  http://your.company.com:8086/mobileserver
   4. Press Deploy Mobile Server to proceed.
      
      

7. Any errors which occurred will be displayed in the window which follows. 

   1. If deploying on Windows, Tomcat will be automatically restarted by the installer.  Alternatively, you can restart tomcat using 'Services' in windows.
   2. Linux users will get a reminder to restart Tomcat.  If you deployed using Linux, you will need to update the ownership and restart tomcat.  Please see Linux Preparation for details.