Setup and Run Admin Tools, Backup My Org, and Clean My Org

Step-by-step guide

1. From the "Content" tab in ArcGIS, select "New Item” → “Application" → “Other Application”. Press “Next” button.

Open

New Item Button in ArcGIS Content Tab

Open

Application Button in New Item Modal

Open

Application Type in New Item Modal

2. Name the application "Admin Tools”, “Backup My Org”, or “Clean My Org”. Fill in the values for your application. Click “Save” button.

Open

Title Section in New Item Modal

3. Navigate to the "Settings" Tab of the newly created GEO Jobe application.

Open

Settings Tabs in the Application Item

4. From the “Settings” tab, scroll down to the "Application" section. This is where you will find the client/app ID needed for setting up your GEO Jobe build.

Open

Client ID Box in Application Section

5. Add your GEO Jobe application’s portal URL/domain name (HTTP and/or HTTPS) to the “Redirect URLs” input box.

Open

6. In some cases, an application URL is required in the “URL” field (shown in the image below). This can be any placeholder URL. Simply add your own, or enter https://geo-jobe.com into the input box.

Open

Placeholder URL Populated in URL Input Box

6. Be sure to “Save” your settings before attempting to connect the GEO Jobe application to the ArcGIS redirect endpoint.

Open

Conclusion

You should now have the OAuth App ID and Redirect URIs necessary to start the Admin Tools Installation.

1. Export the certificate from IIS:
   a. Open the IIS Manager
   b. Click on the server name in the "Connections" pane (located left-hand side) 
   c. In the middle pane, double-click on "Server Certificates"
   d. Select the certificate you want to export
   e. Click "Export" in the "Actions" pane (located on the right-hand side)
   f. Follow the wizard to export the certificate as a .pfx file (Note: remember the passphrase you specified to protect the cert)
   g. Export the PFX to your GEO Jobe product’s main folder
   (Note: if you don’t have an export option you may need to re-import the certificate to IIS with the allow export option)
   
   

2. Open the command prompt and navigate to the Admin Tools 2.0, BackupMyOrg, or CleanMyOrg directory and insert:

(Note: This will save the passphrase as an encrypted string in the MongoDB database.)

3. In the product’s main application directory, locate the config/nodeconfig.json and make the following modifications in the JSON file:

   "useHTTPS": true,  "certs": {     "certificate": "",     "key": "",     "pfx": "ADD PFX FILE NAME HERE"   },

(Note: If you are using an absolute path in your nodeconfig.json, be sure to use double backslashes, such as "C:\\BackupMyOrg\\Certificates\certificate.pem" or "C:\\CleanMyOrg\\Certificates\certificate.pem". Please also ensure that the name of your PFX file is added to the “pfx” property. An example shown above.)

4. Restart your Admin Tools 2.0, Backup My Org, or Clean My Org server app or service.

   1. Then, load https://localhost:9181 or https://yourwebdomain:9181 (for Admin Tools 2.0), https://localhost:8500 or https://yourwebdomain:8500 (for Backup My Org) or https://localhost:8000 or https://yourwebdomain:8000 (for Clean My Org) into your browser.

1. Both a certificate and key .pem file are required. (If you need to generate these, you can do so by downloading OpenSSL at: https://slproweb.com/download/Win64OpenSSL_Light-3_2_0.msi

2. Open the command prompt in Windows.

3. Run the following commands to generate your private key and public certificate:

4. Once you have the cert and key files, copy them to your Admin Tools, Backup My Org, or Clean My Org main folder.

5. Edit the config/nodeconfig.json file and make the following modifications:

4. Restart your Admin Tools 2.0, Backup My Org, or Clean My Org server app or service.

   1. Then, load https://localhost:9181 or https://yourwebdomain:9181 (for Admin Tools 2.0), https://localhost:8500 or https://yourwebdomain:8500 (for Backup My Org) or https://localhost:8000 or https://yourwebdomain:8000 (for Clean My Org) into your browser.

See A "Not Secure" Warning On Your Browser?

If you have created a self signed certificate, those will always appear as not trusted.

You will need to buy a certificate from a trusted source (such as Verisign) to have a signed certificate from an authority.

Open

To convert an IIS certificate to a .key and .pem format for use in Admin Tools 2.0, Backup My Org or Clean My Org, you can follow these steps:

1. Export the certificate from IIS:
   a. Open the IIS Manager
   b. Click on the server name in the "Connections" pane (located left-hand side) 
   c. In the middle pane, double-click on "Server Certificates"
   d. Select the certificate you want to export
   e. Click "Export" in the "Actions" pane (located on the right-hand side)
   f. Follow the wizard to export the certificate as a .pfx file (remember the password you specified to protect the cert)
   (Note: if you don’t have an export option you may need to re-import the certificate to IIS with the allow export option)
   
   

2. Convert the .pfx file to a .pem file using OpenSSL:
   a. Install OpenSSL on your computer if it is not already installed (Windows version can be found at: Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions
   b. Copy the .pfx file to the OpenSSL /bin folder
   c. Open a command prompt or terminal window
   d. Navigate to the openSSL bin directory
   e. Run the following command (changing exported cert name as necessary):

This command will prompt you for the password you used to protect the .pfx file. Enter the password and press Enter. The command will create a .pem file in the same directory as the .pfx file.

3. Extract the private key from the .pem file using OpenSSL:
   a. Run the following command in the same directory where the .pem file is saved:

This command will extract the private key from the .pem file and save it as a separate .key file in the same directory.

4. Copy the .pem and .key to the application directory and configure config/nodeconfig.json
   a. Copy the new .pem and .key file to your application root directory
   b. Open <application directory>\config\nodeconfig.json
   c. Modify the settings as follows (changing names as necessary):

5. Restart the Admin Tools, Backup My Org, Clean My Org server and open the browser using HTTPS location.