[toc]
Telligent Community Mobile server components enable the mobile web and native mobile experiences for existing Telligent Community installations.
Installation notes
- If you open the Telligent Community Mobile zip file using Internet Explorer or Chrome, you may need to first right-click the.zip file and select Properties, then click Unblock if the option is available. Click OK to close Properties.
- If installing Telligent Community Mobile into a subdirectory, settings may be inherited from your parent application's web.config which cause a web.config error when you run your community. In such cases, you will have to add <clear /> or <remove /> elements in your Community web.config file to remove the additions made in your parent web.config.
- The instructions for creating an application pool assume you're using IIS7. If you're using IIS6, see the Microsoft documentation.
- .NET framework version 4.5 is required for Telligent Community Mobile.
- If you're using Windows Server 2008, your user is IIS APPPOOL\<application pool you create>.
- Telligent Community Mobile requires Telligent Community 8.5+.
Obtain Telligent Community Mobile
- Obtain the installation package from the Telligent downloads page.
- Extract the contents of the download to a temporary location on your hard drive (for example, C:\inetpub\TempFolderUnzipBuild\).
Installation components
This installation procedure has been divided by installation area so that multiple administrators can install different aspects of a Telligent Community Mobile.
Zimbra Community mobile website
This procedure assumes you already have |IIS installed, and have configured the Database and Search servers.
Copy the files
Create a web directory folder and copy the files there:
- Create a path to hold the mobile website (for example, C:\inetpub\ZimbraMobile\).
- In the extracted .zip file folder, copy all of the zip file's Web folder contents and paste them into the server's directory folder, leaving the directory structure intact.
Create the website in IIS
- If you are using Windows Server 2008, create a new application pool. (If using Windows XP for development purposes, skip this step.)
- Open Internet Information Services (IIS) Manager.
- If required, connect to your web server.
- In the Connections pane, expand your web server.
- Right-click Application Pools and select Add Application Pool.
- Specify a name for your application pool.
- Ensure that the .Net framework version 4.5 is selected.
- Click OK.
- Create the IIS application.
- In IIS's left pane, navigate to Internet Information Services > [computer name] > Web Sites > Default Web Site.
- Right-click Default Web Site, select Add Application. The Add Application window appears.
- Do the following:
- Enter a lowercase name in the alias field (example: zimbra mobile).
- Select the application pool you created in Step 2.
- Enter the path you created in Step 1 in the Physical path field (example: C:\inetpub\ZimbraMobile).
- Click OK.
- Determine your website service account. This account information will be needed for permissions in the next step and in the Database section.
- If using Windows XP for development purposes, your service account is ASPNET.
- If using Windows Server 2008, Vista or higher, follow these steps to find the service account that your web service is running under:
- Open IIS Manager and navigate to Application Pools.
- Use the value of the identity column to determine your website service account.
- LocalService - NT AUTHORITY\LOCAL SERVICE
- LocalSystem - NT AUTHORITY\SYSTEM
- NetworkService - NT AUTHORITY\NETWORK SERVICE
- ApplicationPoolIdentity - IIS APPPOOL\<app pool name>
- OTHER - runs as the specified user
For further details on optimizing the performance of your web server, see Web Server configuration check-list.
Set file permissions
- Add the network service user to the permission structure. Then grant the website service account required file and folder permissions: read permissions to the web directory (which is the main directory for IIS) and modify permissions for web/filestorage/ and its sub-folders.
- Right-click the Telligent Community Mobile website folder and select Edit Permissions.
- Click the Security tab. (If you are using Windows Server 2008 and above or Windows Vista and above, click Edit.)
- Click Add.
- In the Enter the object names text box, type the name of the service account determined above. Click OK.
- Ensure that the service account is selected in the top pane, and view the bottom Permissions pane to ensure that only the read permission is granted.
- Click OK.
- Right-click the Telligent Community Mobile website folder and select Edit Permissions.
Configure Telligent Community
- As an administrator, navigate to Administration for the Telligent Community site that will be exposed through the mobile application.
- Search for Remoting REST Endpoints and ensure it is enabled.
- Go to Administration > Integration > OAuth Clients
- Click Add Client
- Create the OAuth Client representing the mobile installation.
- Specify a Name for the OAuth Client (for example, Telligent Community Mobile).
- Specify a Description for the OAuth Client.
- Identify the Main URL. This is the root URL for the installation of the the mobile website (for example, http://mobile.community.com/).
- Identify the Callback URL. This is the location of the oauth.ashx file within the root URL for the installation of the Mobile Application Builder (for example, http://community.zimbra.com/oauth.ashx).
- Set Client Type to Confidential.
- Under Allowed Authorization Grants, check Authorization Code and Trusted Client.
When a link is rendered within the mobile UI and the mobile application cannot show the content of the link, the user is directed to the full site. When this redirect occurs, mobile can automatically log the user in if the OAuth client is also granted the Client Credentials grant type. Note that this grant type will not work when using an HTTP-based authentication mechanism, such as Windows Authentication.
- Click Create.
- From Administration > Integration > OAuth Clients, locate the new OAuth Client for Telligent Community Mobile and click Client Credentials. Make note of the Client ID and Secret values. These will need to be supplied during the configuration of the mobile site's web.config file.
Configure the Web.config file
-
-
- Open the web.config file within the root folder of the Telligent Community Mobile site on the server using a plain text editor.
- Locate the <mobile> node and update it:
- Set the evolutionUrl attribute to the full root URL of the Telligent Community site (for example, http://community.telligent.com/ ).
- If Telligent Community is configured to require Windows Authentication, specify a valid Windows user with the networkUserName, networkPassword, and networkDomain attributes.
- Set the urlScheme attribute to a unique value for your app. This will be used by the native app to support URL redirection. It should be set to a unique value containing only alphabetic characters (no punctuation, no spaces, no extended characters). For example, if configuring a mobile experience for telligent.com, the urlScheme could be "telligentmobile"
- Locate the <oAuth> node and update the clientId and clientSecret attribute values to the values of Client ID and Secret from the OAuth Client created in Telligent Community for Telligent Community Mobile.
- Locate the <authorization> node and change the value of the allowAnonymous attribute. Set allowAnonymous to true to allow unauthenticated users to browse the mobile app subject to the permissions granted to the anonymous user. Set allowAnonymous to false to force all users to login or join to use the mobile app.
- Confirm that you can access your site through the mobile app:
- Open your Telligent Community Mobile root URL. This can be done on a mobile device or a desktop web browser.
- Check that the home page successfully loads without error.
- If an error occurs, check that you've followed the above steps correctly.
-
Next Steps
After the server components are setup, see the developer center for instructions on customizing the mobile experience.