TD MOBILE. Guide to Publishing Applications. Product Version 1.2

Transcription

1 TD MOBILE Guide to Publishing Applications Product Version 1.2

2 TD Mobile : Guide to Publishing Applications, Product Version 1.2 The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Last updated: January 9, Legal Notice Copyright Gupta Technologies, Inc. All rights reserved. Gupta, Gupta Technologies, the Gupta logo, Gupta Powered, the Gupta Powered logo, ACCELL, Centura, Centura Ranger, the Centura logo, Centura Web Developer, Component Development Kit, Connectivity Administrator, DataServer, DBIntegrator, Development Kit, ewave, Fast Facts, NXJ, Object Nationalizer, Quest, Quest/Web, QuickObjects, RDM, Report Builder, RPT Report Writer, RPT/Web, SQL/API, SQLBase, SQLBase Exchange, SQLBase Resource Manager, SQLConsole, SQLGateway, SQLHost, SQLNetwork, SQLRouter, SQLTalk, Team Developer, Team Object Manager, TD Mobile, Velocis, VISION, Web Developer and WebNow! are trademarks of Gupta Technologies and may be registered in the United States of America and/or other countries. SQLWindows is a registered trademark and TeamWindows, ReportWindows and EditWindows are trademarks exclusively used and licensed by Gupta Technologies. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Gupta Technologies Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. GUPTA TECHNOLOGIES, INC. SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. This document may describe features and/or functionality not present in your software or your service agreement. Contact your account representative to learn more about what is available with this Gupta Technologies product. Gupta Technologies, Inc Rocky Ridge Drive, Suite 380 Roseville, CA Gupta Technologies.com 2

3 Table of Contents PUBLISHING TD MOBILE APPLICATIONS... 4 PREREQUISITES... 4 INSTALLATION METHODS... 4 Method Method Method CONFIGURING TD MOBILE DEPLOYER... 5 CONFIGURING IIS... 6 IIS TROUBLESHOOTING

4 Publishing TD Mobile Applications TD Mobile applications can be deployed onto either a local or a remote IIS server. This whitepaper explains how to deploy TD Mobile applications to an internet server. Prerequisites Before publishing an application onto an Internet Information Services (IIS) server, ensure that the following IIS components are installed: ASP.NET 4.5 on Windows 8 or Windows Server To install ASP.NET 4.5 on Windows 8 or Windows Server 2012, use one of the following options: o Run the following command from an administrative command prompt: dism /online /enable-feature /featurename:iis-aspnet45 o For Windows 8 client computers, turn on "IIS-ASPNET45" by using the Turn Windows Features On/Off dialog: Internet Information Services-> World Wide Web Services -> Application Development Features -> ASP.NET 4.5 o For Windows Server 2012 computers, enable "IIS-ASPNET45" using the Server Manager: Web Server (IIS) -> Web Server ->Application Development -> ASP.NET 4.5 Security Static and Dynamic Compression (suggested) Management Console (suggested) Note: If you install an application on Windows 8 or Windows 2012 that attempts to install ASP.NET 4.5 using aspnet_regiis -I, the application will fail to enable ASP.NET 4.5. This option is not supported on either of these operating system versions. Installation Methods There are three ways to publish TD Mobile applications to a Web server. Choose the method that is easiest for you. Method 1 Use the TD Mobile IDE to publish the application to either a local or remote server. Step 1: Open the application using the TDM IDE Step 2: Click on the Settings tab. Complete the needed details to publish. You will need to define Server Name, Server Path, User Name and Password. 4

5 Server Name: The name of the server where the IIS environment is configured. You can use localhost as the Server Name to publish applications to a local server. This can be a name or an IP address. Server Path: The name of the application. It can be an absolute path for the deployment (e.g. C:\inetpub\wwwroot, C:\otherplace). If a relative path (e.g. myapp), then the resource will be deployed under the wwwroot directory, within the given folder name. If empty, the resource will be deployed under the wwwroot directory, within a folder having the name of the application to be deployed. User Name: The name of the user who has Administrative privileges on the server. This user needs to have full Read/Write permissions to the Server Path folder. If deploying on a domain, it should be in the form domainname\username. It can be empty when deploying to localhost. Password: The password for specified user name. It can be empty when deploying to localhost. Method 2 Run TD Mobile using a command line to publish the application to either a local or remote server. Run TD Mobile in command mode as below: Gupta.td.ide.exe batch -p -pusr=domain\user -ppwd=password - psrv=servername <application to deploy> To see more command line options, from a command prompt run Gupta.td.ide.exe batch /? For example, the following command will deploy an application named test, under default IIS root folder (C:\inetpub\wwwroot\test) on local computer (localhost): Gupta.TD.IDE.exe batch -p -pusr=demo -ppwd=demo C:\TDMAPPS\test\test.apx Method 3 From Windows Explorer, right click on the folder and copy the entire application folder and dependencies, excluding the source, to the IIS root folder. Configuring TD Mobile Deployer The TD Mobile Deployer installs the required runtime dependencies on the server machine. Run the TD Mobile Deployer on the IIS server machine after publishing the application. Note that this is a one-time only requirement. The TD Mobile Deployer is found in the \Deployer subfolder of the TD Mobile installation folder. Depending on your installation, it could be a 32-bit or a 64-bit edition, respectively named tdmdeployer_32bit.exe and tdmdeployer_64bit.exe. Transfer the appropriate one to your IIS server machine and run it. 5

6 Configuring IIS Please visit Understanding Sites, Applications, and Virtual Directories on IIS in order to learn more about IIS web applications. Perform the following within IIS Manager after completing the Publishing and Deploying Setup steps above. Step 1: Open IIS Manager. Step 2: Within IIS Manager, make sure your application is listed under the default website. Step 3: Convert your folder to an application (if it is not already converted). To do this, right-click on the folder and select Convert to application. Step 4: Make sure the application uses.net 4 as the default pool. To do this, highlight the application and click on Basic Settings from the Actions pane shown on the right side. Click on the Select... button to see the available application pools. Select a pool based on.net v4. 6

7 You can use an existing pool or create a specific one that you can configure with your preferred settings. During successful deployment process, the TDMobile IDE creates a.net v4 pool named TDMobilePool for you. You can use that one. 7

8 IIS Troubleshooting Problem: Error Internal Server Error when accessing the application. Remedy: Make sure that ASP.NET is properly installed on IIS server machine. Refer to: The reason why we can get this error is the following: The.NET Framework 4 can be installed side-byside with previous versions of the.net Framework on a single computer. If IIS was previously enabled on the computer, the setup process for the.net Framework automatically registers ASP.NET 4 with IIS. However, if you install the.net Framework 4 before you enable IIS, you must run the ASP.NET IIS Registration tool in order to register the.net Framework with IIS and create application pools that use the.net Framework 4. There are two IIS Registration Tools that ship with the.net Framework; one for standard 32-bit systems and one for 64-bit systems. The tool for 64-bit systems is located in the Framework64 directory of the Microsoft.NET directory inside the Windows folder; for example: C:\WINDOWS\Microsoft.NET\Framework64\v would contain the IIS Registration Tool for a 64-bit installation. Open a command prompt as administrator, navigate to the proper Windows directory based on your machine (32-bit or 64-bit) and run aspnet_regiis -r Problem: Publish failed: Unable to share folder: Some or all identity references could not be translated. Remedy: Make sure the user has proper permissions for the IIS root folder. Create a shared directory manually and give full Read and Write permissions to the user. 8