Sana Mobile

Install Sana Mobile App

  To be able to use Sana Mobile app the Webservice add-on must be included in your Sana Commerce license.

The 'Apps' folder is automatically created in the Sana Commerce root directory when you install Sana Commerce on the Web server. The Sana Commerce installer also creates a virtual directory in Internet Information Services (IIS) Manager, called 'apps', which maps to the 'Apps' folder on the Web server.

By default the 'Apps' folder is empty as the Sales Assistant Mobile app is delivered as an add-on.

To install the Sales Assistant Mobile app:

Step 1: The Sales Assistant App package can be downloaded from the Sana Community web site. Only the registered Sana partners can access Sana Community. If you are a customer and you want to install the Sales Assistant App package, please contact your Sana partner or Sana project manager.

Step 2: Unpack the package.

Step 3: Copy the unpacked 'Sales Assistant' folder with all its contents to the 'Apps' folder of your Sana Commerce solution. Make sure that the folder structure is now like this:
   <Sana Commerce root folder>
     <'Apps' folder>
       <'Sales Assistant' folder>
           contents of the Sales Assistant App

Step 4: Currently it is not possible to run apps under 'Basic Authentication' because the Sana Shell, the App in the App Stores, needs to access the app on the server with anonymous access rights.

Since the installer, when installing with deployment type 'Beta', enables basic authentication for the frontend folder, this has to be turned off explicitly on the 'Frontend\Apps' subfolder in IIS.

To accomplish this, open IIS, lookup the 'Frontend\Apps' virtual directory and enable 'Anonymous Authentication' and disable 'Basic Authentication' on it.

The same should be done for the 'Frontend\content\files' folder to make sure that images will be retrieved by the app.

In the Frontend directory of the Sana Commerce solution create an empty folder: Frontend\product\images. In IIS enable 'Anonymous Authentication' for the 'images' folder and disable 'Basic Authentication'.

If you use IIS 6 or older, you should also register the 'application/json' MIME type and add the 'Access-Control-Allow-Origin' custom HTTP header: 1. Open IIS and locate the 'Apps' virtual directory. 2. Right-click on the 'Apps' virtual directory and select 'Properties'. 3. Switch to the 'HTTP Headers' tab and in the 'Custom HTTP headers' section click 'Add'. 4. In the 'Custom header name' field enter 'Access-Control-Allow-Origin' and in the 'Custom header value' enter '*'. 5. In the 'MIME types' section click on 'MIME Types…' and then 'New…'. 6. In the 'Extension' field enter '.appmanifest' and in the 'MIME type' field enter 'application/json'.

Step 5: Because Apple will require HTTPS connection for iOS apps by the end of 2016, connection to your web shop the Sana Mobile app connects to should be secure. Therefore, it is required to configure secure data exchange for the web shop. For more information about how to set up secure connection for your web shop, see 'HTTPS'.

The Sana Web service should also work over HTTPS. You should modify the 'web.config' file of the Sana Web service. It is located in the 'WebService' folder of the Sana Commerce solution. Comment out the default binding and endpoint and uncomment those which are used for HTTPS connection.

The Sales Assistant Mobile app is now installed.

  In Sana Admin > Setup > ERP integration> Index fields you should add the 'Last Date/Time Modified' field to the Filter fields. This is the required index fields configuration for the app to be able to retrieve the modified products during data synchronization.

See also:
Supported Devices & Scenarios
Mobile App Getting Started
Sana Mobile App
Mobile