GAM Backend is a web application that allows the GAM administrator to manage GAM Repository users, GAM Roles, GAM Security Policies, etc.
The actions that can be performed using the GAM backend application consist of the administration of:
The application is distributed by GeneXus when Enable Integrated Security property is set to TRUE (which we call compiled GAM backend). GeneXus distributes a .zip file with the compiled binaries that are unzipped at build time. In the case of .Net, the file is unzipped in the web directory; in the case of Java, in a folder called GAM_Backend, which is included the web directory and will be copied to the web server afterwards.
For executing the compiled GAM Backend, there is an option available on the menu: Build -> Run GAM Backend.
Also, it is possible to access it by executing an URL like this one:
- NET: http://<server>/<baseURL>/gam_dashboard.aspx
- JAVA: http://<server>/<baseURL>/servlet/genexus.security.backend.gam_dashboard
Take into account that the first screen that may be displayed when executing the compiled GAM Backend is the Web Panel GAM_login to enter the administrator credentials.
Apart from the compiled GAM backend, the GeneXus objects can be imported into the Knowledge Base, by importing GAM_Web-Administration.xpz found in <GeneXus Installation>\Library\GAM.
These objects are useful because they are examples of use of the GAM API. They can be changed as desired by the GeneXus developer if some requirements are not met (the GAM API is available for that purpose).
NOTE: The GeneXus objects of the .xpz file have different names than those of the compiled binaries.
By default, only administrator users are allowed to execute the GAM Backend; see Restricted access to GAM Backend for more details.
The gamexamplelogin is part of the GAM front-end objects and is distributed by GeneXus. The same happens with the gamhome object.
After having activated GAM, if you execute the gamexamplelogin object, or gamhome object (which will redirect to the gamexamplelogin if you are not logged in), you will be asked to configure a Home Object for your application.
If the backend was already imported, the GAMExampleWWUsers object or any other object of the backend must be set as the main object to be generated. Due to the change in the GAMHome object, which is no longer referenced to any object in the backend if it was already imported, it is not generated. When the .xpz file is imported, that object is already modified and set as main.