Page Comparison

There are several options presented when the graphical installer is opened. Once the installer has been launched you are presented with a menu of options.  We will focus on the "Deploy new mobile server" option 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.

...

1.   Click to select and you will be prompted for the Tomcat path. 
   
   1. Choose browse, and navigate to the home directory for

...

1. 1. Tomcat. This is the directory which contains the bin, lib, webapps, etc subdirectories. Choose open to

...

1. 1. 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.

...

1. 1.   Any user which can create

...

1. 1. databases can be used

...

1. 1. , 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

...

1. 2. Your new schema name should now appear in the line next to Schemas.
   3. Click Test Connection to ensure that the mysql setup is working as intended. If it is correct, the Next button will now be clickable.
   4. Click Next to continue.
      
      

2. 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.

...

1. 1. 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.
   2. Choose Test Connection to proceed.
   3. The next button will be clickable if the connection test succeeded.
   4. Click next to continue.

...

1.  

2. 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.

   1. Any errors will be displayed and will also be added to the logs.
   2. Assuming there are no errors, click next to proceed.
      
      

3. 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

...

1. 1. 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, as above.
   3. You can choose to run the administrative console and the server servlets on different ports. 
      1. This would be done in the case where you want to open your firewall only to specific IP addresses to use the administrative console. 
      2. Your firewall must be open to all IPs from which your users would log in to Swift MEAP from their devices. Typically this is all IPs. 
      3. In this basic installation guide, we will assume both are running on the same port, 8080, which is

...

1. 1. 1. Tomcat's default. 
   2. Press Deploy Mobile Server to proceed. 

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

   1. If deploying on Windows,

...

1. 1. Tomcat will be automatically restarted by the installer.
   2. Linux users will get a reminder to restart

...

1. 1. Tomcat. 
      1. However, Linux users need to do one more step before restarting

...

1. 1. 1. Tomcat. 
         1. The directory

...

1. 1. 1. 1. $Tomcat_HOME/webapps/mobileserver is owned by root, and must be owned by the

...

1. 1. 1. 1. Tomcat user. 
         2. Please change ownership of this directory before restarting

...

1. 1. 1. 1. Tomcat. (i.e., chown -R

...

1. 1. 1. 1. Tomcat7.

...

1. 1. 1. 1. Tomcat7 /var/lib/

...

1. 1. 1. 1. Tomcat7/webapps/mobileserver) 
         2. Once the directory's ownership has changed, restart

...

1. 1. 1. 1. Tomcat. 

If all has worked, your Swift MEAP server is now available at 

http://yourhost.com:8080/mobileserver

• You can log in to the Swift MEAP server using admin/admin as the username and password. 
  • It will immediately ask for a new password.
• At this point, it will present to you the license screen. Please see our /wiki/spaces/SMSAGV/pages/213922 for further information.