Post-Deployment Server Configuration
Once you have physically deployed your Info application to the production server for the first time, you need to configure it to run in the new environment.
When Using Windows IIS Web Server
- Provide a Logi Info license file for the application, unless you're using a centralized v12 license file.
- Register the application with IIS. You can do this using Studio (if you've installed it on the production server), Server Manager, or the IIS Manager tool.
- Ensure that the datasource connection strings or parameters, constants, and other server-specific attributes are correct in your application's _Settings definition. This can be done using Notepad if Studio is not installed.
- If your application writes any output to the file system outside of your Logi application folder, ensure that the account the web server uses to run your application (ASP.NET, NETWORK SERVICE, or Application Pool, depending on IIS version) is granted Write permission to the relevant folders.
When Using a Java Server
- Provide a Logi Info license file for the application, unless you're using a centralized v12 license file.
- Provide any additional configurations required for your server. See Java Server Configurations for specific information.
- Ensure that the datasource connection strings or parameters, constants, and other server-specific attributes are correct in your application's _Settings definition. This can be done using any text editor.
- If your application writes any output to the file system, ensure that the identity the application runs under has appropriate file access permissions for the relevant directories.
Subsequent deployments for the purpose of updating report definitions, images, XML data, etc. should not require you to do any of the steps discussed above, unless you're changing folder locations or _Settings attributes. This means Logi Server Engine files and _Settings.lgx can be left out of future deployments undertaken for simple update purposes.