Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

NOTEKeep in mind that this install guide represents the minimum steps needed in an ideal environment with no variables or complications to overcome. It is not meant to serve as a comprehensive solution to any and all installation workflows and environments. Enterprise expertise is still essential for handling this installation. 

  • If you are unsure about whether Admin Tools for Portal can be installed on your infrastructure, please visit our product page, and contact us to request a technical meeting to discuss installation. We do sell Professional Services Installation Packages as an additional option to the purchase of Admin Tools for Portal.

1. Requirements for receiving a licensed build from GEO Jobe

In order to receive a licensed build of Admin Tools for Portal, the following information must be provided to GEO Jobe.

Regarding Registering Admin Tools for an OAuth App ID (for Non-IWA):

Add a brand new application, call it "Admin Tools", and register that one. That will generate an "App ID" (NOT THE SAME AS THE ITEM ID). Then, add the full URL of where admin tools will be running from (i.e. http://domain.com/admintools/ and/or https://domain.com/admintools/) to the "Redirect URIs" on the Admin Tools application.

Note: The application doesn't have to actually DO anything, it just has to exist and be registered, that way we can log in. It acts as is the gate Admin Tools goes through.


2. Request a new build from GEO Jobe

All of the above information will be stored in our license database so that any future builds will already contain your App IDs and Portal URLs. We use this information to generate a custom build just for your environment.

3. Unzip the contents to the zip file provided by GEO Jobe

Unzip the contents of the zip file to the web-accessible directory provided to GEO Jobe in step 1.

4. Convert the folder in IIS to an application

Convert the folder from step 3 into an application.

Application Server Installation (Windows)

1. Requirements for hosting the Admin Tools Server

The Admin Tools Server application is written in JavaScript and runs on Node.js. It is recommended that Node.js be installed on the machine hosting the application, however it is not required. See: Installing Without Node.js on the Web Server.

2. Install MongoDB

  1. Download MongoDB 3.4.1 Windows x64 and install.

  2. If there are any issues, see the MongoDB Installation Guide.

  3. Configure a Windows Service for MongoDB

NOTE on Mongo.cfg

NOTE: Do NOT use tabs in the mongo.cfg


3. Install Required IIS Modules

The following IIS modules must be installed for Admin Tools for Portal. The URL Rewrite and Application Request Routing extensions are used by the application to create a reverse-proxy to forward requests through IIS To the Node.js server application.

4. Install Required Node Modules

  1. Open your cmd prompt & navigate to the Admin Tools 'app-server' directory.

  2. Run the following command: npm install.

NOTE: Step 4 does require communication with the internet. If your server does not have internet access, then copy the Admin Tools files to your local machine, run the command, and copy the 'node_modules' folder to the server.

5. Install Windows service

Open a command prompt as an administrator in the app-server folder located in the root of the application.

  1. Run nssm install "Admin Tools Server"

  2. Path: choose the node.exe in the app-server folder or C:\Program Files\nodejs\node.exe if Node.js is installed.

  3. Startup directory: choose the app-server folder.

  4. Arguments: dojo/dojo.js load=app/Bootstrap

  5. Click Install Service



NOTE: The service can be removed with: nssm remove “Admin Tools Server”

6. Start the server

Using Windows Service Manager, start the Admin Tools Server service.



  • No labels