SuperOffice Pocket crm installation Guide SuperOffice

Mobile phone installation explained

iPhone / iPad installation

1. 
   Navigate to the Pocket CRM distribution server (i.e. http://m.yourcompany.com/dl) and select ”1. Install Pocket CRM from App Store”
   

2. 
   Install Pocket CRM from the Apple App Store.
   

3. 
   Go back to the browser and select the ”2. Click to configure Pocket CRM” link.
   
4. 
   Pocket CRM should be configured and ready for login.. Click ”Login”
   

Android installation

1. 
   Navigate to the Pocket CRM distribution server (i.e. http://m.yourcompany.com/dl) and select ”1. Install Pocket CRM from Google Play”
   
2. 
   Download and install Pocket CRM from Google play.
   
3. 
   Go back to the browser and select the ”2. Click to configure Pocket CRM” link.
   
4. 
   Pocket CRM should be configured and ready for login.. Click ”Login”
   

Other devices

Step 1: Navigate to http:/// Example: http://m.yourcompany.com/dl Click “Download” to automatically detect correct client installation. Click “Manual download” to override and select the client type you want to install.	Step 2: Follow the instructions and complete the installation.	Step 3: Locate Pocket CRM and start it. Typically installed in the “Programs” folder. The first time it will use some time installing configuration.

Example Nokia E71: Menu > Tools > Settings > General > Personalisation > Home screen > Mode settings > Home screen applications > Application shortcuts.

After running the installer on the server a set of configured mobile phone clients are installed into the distribution server.

C:\Program Files\Apache Software Foundation\Tomcat 6.0\mBricks\dl\distributionServer\apps\1\ (1,2,3,4,5)

Read Platform support below to see what the different clients are.
Inside a SuperOffice.jad-file:

After installation

Locating Pocket CRM

Set application permissions

To ensure a good user experience the user should grant permissions to the application before the application is started. The most important is access to network; this will result in getting fewer dialogs during start-up and use. The way to set the permission is different from one mobile phone to the other. E.g. on Nokia phones you must open Control Panel -> Application Manager -> Installed Applications -> SuperOffice Pocket -> Options -> Settings -> Network Access and then set "Always allowed" or "Ask first time only".

Phone settings

The Pocket CRM is a connected application and network need to be setup and configured before the application can launch. To setup network on the device the APN (Access Point Name) for Internet must be defined. The operator normally already configures this when the phone is purchased, but if it is not please first check if your operator has an online OTA (Over the Air) configuration service. Most of the operator provides such a service. To configure the APN manually, please check your phone manual and your operator settings.

Tip: On older Blackberries you must manually configure APN, this is done under Options -> Advanced Options -> TCP/IP.

Recommended enterprise scenario

A Network Load Balancing cluster (NLB) should be considered if there are more than 100 users of SuperOffice Pocket CRM. This is also related to the NetServer being a prerequisite; please see NetServer documentation for details about setting up NLB.
This scenario can be illustrated as follows:

Protocol and service used for the different arrows
1)	HTTP, default port 80 (AES Encrypted content)
2)	Web services (HTTP)
3)	IMAP
4)	File Share (may vary according to document archive provider)
5)	Database proprietary protocol (as implemented by the database drivers)

Installing on multiple hosts

In an enterprise scenario it is recommended to install Pocket CRM on a separate host to share the workload. Several hosts will be able to serve a greater number of clients if proper Network Load Balancing is used.
Note: A large enterprise already hosting a Java enterprise environment (JEE), typically on IBM WebSphere, JBOSS, or equivalent, it is advisable to deploy Pocket CRM into this environment instead of using the built-in Apache Tomcat application server. Describing or performing such a deployment to such an environment is beyond the scope of this installation guide and features of the installer it-self. This should be deployed in collaboration with a SuperOffice partner.
The simplest way of installing on multiple host is to separate Pocket CRM and NetServer on two separate physical hosts. For this scenario you can still use the exact same installation described for the small scenario.

Appendix A: Phone requirements

SuperOffice Pocket CRM is designed to support a wide variety of mobile phone brands and models.
Almost all mobile phones on the market today supports download and installation of applications created using Java technology (“Java ME” / “J2me”).
Required Java spec:

• 
  Mobile Information Device Profile (MIDP) version 2.0
  
• 
  Connected Limited Device Configuration (CLDC) version 1.1
  

For the Android platform we have created a special package with native support for camera and touch keyboard.

For the Apple iPhone (iOS) we have provided a separate package that is installed from the App Store.
Minimum supported screen resolution is QVGA. This is a resolution of 240 by 320 pixels, supporting both landscape and portrait orientations. The layout and graphics scales to fit larger screens, like 320 by 480 or even larger screens. Smaller screens than QVGA are not supported.
SuperOffice Pocket CRM supports both touch screen and non touch screen phones. Support for various keyboard layouts, like the common mobile multitap or full QWERTY layout are implemented.
SuperOffice Pocket CRM is an online application that needs a network from the mobile phone to the Pocket CRM server. All data traffic is compressed and is designed to have a minimum overhead to save bandwidth. Minimum support is GPRS (approx 114kbp/s) – but 3G (approx 384kbp/s – 2Mbp/s) support is recommended. At home or in the office wireless LAN could be used to keep data traffic costs down.
SuperOffice provides a list of recommended phones.

Appendix B: Application security

SuperOffice Pocket CRM provides full security of all traffic going between the client installed on the end-users phone and the server. All data traffic is encrypted using strong AES Encryption.

Client side security

Pocket CRM client application is signed using various certificates from various vendors. A signed client application provides the end-user with a trust that the application is not altered in any way. It also provides a mechanism for giving trusted access to various features and APIs on the phone.
In case of a lost mobile phone the user must change the password to avoid possible data theft. Pocket CRM uses local caching to speed up data access – this data is stored locally in the phone, but not commonly accessible on the mobile phones file memory / file system.

Server side security

Pocket CRM need to be installed in a way so that the client on the mobile phone can access the server from the internet. A common way is to install Pocket CRM server in DMZ. Pocket CRM server need to access SuperOffice NetServer. It is recommended that SuperOffice NetServer is installed inside the local network, not in DMZ. However, if for practical reasons you need to install Pocket CRM and NetServer on the same sever it is highly recommended that you lock down IP access to NetServer (Web Services).
This can be done in Internet Information Services (IIS) Manger:

• 
  Right-click NetServer installation under Web Sites and select Properties
  
• 
  Select Directory Security tab and click Edit in the IP address and domain name restrictions
  
• 
  Select Denied access and add select the server that is allowed, i.e. PocketCRM server
  

Appendix C: Windows Server 2008 prerequisites

The SuperOffice Pocket CRM installer uses IIS 6 administration tools when installing the IIS components.
Before installing on Windows Server 2008 you need to install some role services using the Server Manager. (This assumes that the server already has the Web Server (IIS) role installed.

• 
  Log on to the Windows Server 2008 as administrator
  
• 
  Open Start > Administrative Tools > Server Manager
  
• 
  Select Roles node and select Add Role Services under Role Services
  
• 
  Under node Management Tools select IIS 6 Management Compatibility
  
• 
  Click Next and Install
  

Appendix D: Server configurations

GSM formatted phone numbers

When initiating phone calls from Pocket CRM it is important that the numbers are formatted in a way that the phone can use. SuperOffice NetServer has the functionality to return all phone numbers from the SuperOffice database in a clean formatted way, without spaces, commas and including country prefix, like this: +4712345678

To enable this feature in NetServer make sure that in Web.config contains this element:

Apache Tomcat port

SuperOffice Pocket CRM is bundled with an Apache Tomcat application server. The installer installs this server into default installation directory and using default listening server port – 8585. For some server environments certain ports are locked down by firewall hardware/software so the listening port needs to be changed.
To change Apache Tomcat listening port:

• 
  Edit C:\Program Files\SuperOffice Pocket CRM\Tomcat 6.0\conf\server.xml using WordPad
  
• 
  Change connector port from 8585 to the new port, ex 8686
  
• 
  Change connector executor from 8585 to the new port, ex 8686
  
• 
  Restart Pocket CRM service (Start > Administrative Tools > Services)
  

Using non-default port

For installations on a server running Microsoft Internet Information Server (IIS) a filter is by default installed that will forward traffic going to IIS (default on port 80) forward to Apahce Tomcat running (default running on 8585). This way IIS and Tomcat can both share the same port externally (default port 80) and avoid opening extra ports in the firewall(s).

If IIS is set up using a different port then default port 80, or you want to connect directly to Tomcat you need to remember to add this port during installation. Server address is used when configuring clients, if you plan to use a different port than default port 80 you need to insert this during installation, like this:

Appendix E: Log files

Pocket CRM provides flexible logging on the server-side.

Pocket CRM server

These log-files are placed in the \logs folder, example:

C:\Program Files\Apache Software Foundation\Tomcat 6.0\logs

Inside logs you will find separate log files, each named according to which Server address (URL) the server application got during installation, example: PocketCRM.log
(Unexpected errors during runtime can also end up in a separate log files, stdout_yyyymmdd.log or stderr_yyyymmdd.log.)

Distribution server

The distribution server has a separate log file for logging mobile brand/model downloading and installing the Pocket CRM application. This log file is located according to which Download address (URL) the distribution service got during installation, example:

C:\Program Files\Apache Software Foundation\Tomcat 6.0\mBricks\dl\distributionServer\log\download_history.log

Appendix F: AJP Connector

NOTE: The ISAPI connector used in Pocket CRM 1.x, 2.x and 3.0 has been replaced with an improved .NET based AJP Connector. Please uninstall Pocket CRM 1.x, 2.x and 3.0 before installing 7.0
Part of the default installation of Pocket CRM is a connector that forward traffic from IIS to the embedded Apache Tomcat server running on port 8585.
The connector is a .NET based DLL that is installed on /bin/ajp/

During installation Virtual Directory (Application) are added for both Pocket CRM (/pocketcrm) and Distribution Server (/dl). Both these Virtual Directories points to the /bin/ajp/ and have asp net handler mappings defined.

Virtual Directories defined for each Pocket CRM installation:


Handler mapping installed on each of the Virtual Directory (Application):

The Handler is configured with Script access.

The scripts installing Virtual Directories and Handler mappings are stored in /ajp

Page