The purpose of this document is to explain how to take the binaries to production, of an application that uses GeneXus Access Manager (GAM). To import the data of the GAM database into production, refer to GAM Deploy Tool.
- See How to deploy .NET (C#) WEB application for information on deploying Net applications.
- After having created new Repository Connections in the production database, update connection.gam file using GAM Deploy Tool. Afterwards add connection.gam file and application.gam file to the virtual directory.
- In case of SD applications, add Metadata folder under the virtual directory.
- In case of SD applications, add gxmetadata folder under the virtual directory, only the <main_object>.<plataform>.json files for security.
- Add all the GAM libraries to the deployment. Depending on the DBMS used, they are located under <GenexusInstall>\Library\GAM\Platforms\. Copy the Artech.Security.*.dll files.
- Deploy the application as explained here: How to deploy a Ruby application: Linux setup for running Ruby applications
- After having created new Repository Connections in the production database, update connection.gam file using Deploy Tool. Afterwards add connection.gam file and application.gam file to the virtual directory.
- In case of SD applications, add Metadata directory under the virtual directory.
- In case of SD applications, add gxmetadata directory under the virtual directory, only the <main_object>.<plataform>.json files for security.
- Add all the GAM libraries to the deployment. Depending on the DBMS used, they are located under <GenexusInstall>\Library\GAM\Platforms\. Copy all the .rb files.
In all platforms, take into consideration: Going into production: checklist for Applications using GAM