The most current version of OnPoint is 6.4

OnPoint 6.4 contains several new features and enhancements. These include but are not limited to: the use of a dashboard page and bar, enhanced search and filtering functions as well as many UI enhancements. Please consult the Application Design Guide located in the OnPoint 6.4 installation package to learn about all the new features and enhancements included in version 6.4

Please refer to the following link to see an overview of whats new in 6.4:
http://www.oriongis.com/downloads/OnPoint_6.4_Whats_New.pdf

Please send an e-mail to support@oriongis.com requesting a download link for OnPoint 6.4. A member of our Support Team will provide you a download link for the OnPoint 6.4 installation package as well as provide instructions regarding obtaining a new license.

When you request a download link for 6.4, our Support Team will include, in its response, instructions regarding acquiring a new license file.

Here are the steps:
1- Send an email to license@oriongis.com requesting an OnPoint Product Key (please include contact information: name, organization, e-mail, phone, etc).
2- Once you receive your OnPoint Product Key, launch the License Requestor Tool that is installed along with OnPoint 6.x and generate the .REQ file and save it to a file.
3- Email the .REQ file to license@oriongis.com.
4- Once you receive your license, place it under the license folder (C:\Rolta\OnPoint6.x\license). Ensure that the file itself has modify permissions for the NETWORK SERVICE AND ASPNET users. Restart your IIS and this will activate your OnPoint 6.x application.

All current OnPoint users are eligible to upgrade their production license to a one year renewable 6.4 production license. Current users are also eligible to test out 6.4 in a development environment for 3 months. If you require any additional licenses or extensions or are a new customer who would like to evaluate OnPoint 6.4, please contact Michael Franschman of our Sales Department at mfranschman@oriongis.com

All information regarding the installation of or upgrade to OnPoint 6.4, as well as migrations, is included within the Installation Guide located within the OnPoint 6.4 installation package. Please contact support@oriongis.com to obtain a download link.

Please direct any support requests to support@oriongis.com a member of our Support Team will be happy to answer any questions or assist with any issues you are experiencing.

Please contact support@oriongis.com if you come across any issues regarding our software or documentation.

Please contact Michael Franschman (mfranschman@oriongis.com) of our Sales Department if you would like information sheets or performance benchmarks regarding our products.

There are currently no enhancement or service packs available for OnPoint 6.4, when one becomes available we will provide this information on our FAQ as well as the appropriate download and installation instructions. For information regarding enhancements or service packs for an older version of OnPoint please contact support@oriongis.com

When hot fixes become available, all relevant information will be posted on our website including download and installation instructions.

Please contact Michael Franschman (mfranschman@oriongis.com) of our Sales Department for any inquiries regarding OnPoint extensions

For any information regarding OnPoint versions or feature extensions please contact Michael Franschman (mfranschman@oriongis.com) of our Sales Department

Currently, OnPoint 5.0.x will run on a 64 bit OS. OnPoint 6.x will have full support for 64-bit operating systems later in 2008.

1. Run the OnPoint 6.x installer and choose "Custom Install".
2. Accept the warning regarding AGS Server components.
3 At the OnPoint Components screen, DESELECT ALL the components except OnPoint Website.
4 At the URL definition screen, RENAME OnPointWebsite to your desired instance name.
5 Un-check the boxes for shortcut creation and click Next to create your new instance.
These instructions apply to OnPoint version 6.2 and later.

Check the permission on the file. When you received the license by email from Orion, you may have saved the file on your desktop and later moved it to the license folder. In this case OnPoint will not have permission to access the license file (because the ASPNET in Windows XP and NETWORKSERVICE in Windows 2003 users require modify permission). To correct this, right-click on the license file in the license folder and select properties.

Click the ‘Security’ tab. Click the ‘Advanced’ button. On the ‘Advanced Security Settings' dialog enable the ‘Allow inheritable permissions…’ checkbox. Click OK.

The top banner of your OnPoint Website can be changed to whatever you desire. Here is how it is done:
1- Browse to C:\Rolta\OnPoint6.x\InstanceName\WEB\App_Themes\Theme\Images
2 - Copy your banner logo (as a .jpg) into this directory and rename it to onpointlogo.jpg (be sure to back up your original onpointlogo.jpg incase you need to revert
3 - Refresh your website

Note: Replace InstanceName and Theme with your instance name and theme you are using

When you install over the network using Remote Desktop the permissions a user has are a bit different. Give this one a try: Login to the server and go to Start -> Run and enter the command change user /install and press Enter. This will put you in install mode. Try installing OnPoint again. This should solve the issue.

In order for OnPoint 6 to connect to Oracle it needs the ODP.NET dependency. So make sure it is installed.
You also have to go inside the SQLNET.ORA file and change the value of SQLNET.AUTHENTICATION_SERVICES to NONE. By default it looks like this: SQLNET.AUTHENTICATION_SERVICES=(NTS) change it to SQLNET.AUTHENTICATION_SERVICES=(NONE)

OnPoint 6.x is compatible with Crystal Reports Developer XI Release 2 only.

The OnPoint Administration Tool enables you to build Web-GIS Applications. These applications/web services are stored in a configuration file. To access the Administration Tool the Administrator must be authenticated against an authorized list. This list is managed using the OnPoint Security Console.
Note: Administrator username and password are common to both OnPoint Administration Tool and the OnPoint Security MMC (Security Console) i.e. both use the same username and password.

Go to Start Menu>All Programs>OnPoint 6>OnPoint Security MMC

You will be presented with a Login Screen. This is the authentication prompt for the OnPoint Security Console. The username is “Administrator”. Orion will have provided you with a password. Please note that this password can be modified only when you are logged on to the server on which OnPoint is installed. However, the OnPoint Security Console can be accessed and operated upon from any computer you are using to administer OnPoint.
Upon Successful authentication you will be presented with the OnPoint Security MMC (Microsoft Management Console).

If you are accessing the Security Console for the first time, then click on “Providers”; then click on “Membership Providers”; then click on “Get Providers”. This will establish connection with the Membership Web Service.
Click on Users, Right Click on User “Administrator” and Select “Set Password”. Set New Password for User “Administrator”. Subsequently, you will use this new password to login to the Instance Manager. You may want to add Description for User “Administrator” e.g. your name and change the email address to your email. If you are not able to set the password that means password setting/resetting is not enabled. Click on “Membership Providers”; click on “Options” Tab and check the checkboxes for “Password Reset” and “Password Retrieval”.

Clicking on the InstanceMembership will provide a list of all Instances registered with the Instance Manager. The default Instance created during OnPoint Installation is “OnPointWebSite”.

If there are multiple instances then the Security Console enables you to assign access rights for different Instances to different users (Administrators).
The access hierarchy is as follows:
Define Roles (similar to User Groups)
Define Users and assign User to Role
Assign Resources to Roles (i.e. which Role has access to which Resources).

Default Role is “Administrators”
Default User is “Administrator”
Default Instance is “OnPointWebSite”

This is a result of your choices in the Configuration Set. Any Column that is set as allowed “More Info” (Identify) will appear in the Identify Window. Any Column that is set as “Export” will appear in the XML/XSL Reports.  In the above case you may have allowed “Work Phone” and “Home Phone” Columns for “More Info” but not allowed for “Export”. See example below:

Note: Sometimes you may encounter a Situation where you have defined more than one Configuration Set.  In Configuration Set “A” you set the “Work Phone” Column of Ward Layer as not allowed for Export.  In Configuration Set “B” you set the “Work Phone” Column of Ward Layer as allowed for Export. You have set both Configuration Sets as Private Resources. If User “ABC” has access rights to Configuration Set “A” only, then User “ABC” will not see Work Phone in his/her Reports. If User “ABC” has access rights to Configuration Set “A” and Configuration Set “B” then User “ABC” will see Work Phone in his/her Reports because for each User OnPoint creates a “Union” of Column permissions of all Configuration Sets for which User has access rights.

By default, OnPoint is configured to show a minimum of three (3) search tabs. To change this, you have to make a modification in the surf.skin file located at C:\Rolta\OnPoint6.x\OnPointWebsite\WEB\App_Themes\Surf (assuming OnPointWebsite is the instance you are configuring). With the file open search for the tag SearchLinksVertical and change the MaximumTabCount attribute to the number of search tabs you want visible.

By default, OnPoint is configured to show a minimum of three (3) map tabs. To change this, you have to make a modification in the mapviewer.aspx file located at C:\Rolta\OnPoint6.x\OnPointWebsite\WEB\WebPages\Map (assuming OnPointWebsite is the instance you are configuring). With the file open search for the tag VisibleCount and change the attribute to the number of map tabs you want visible.

1. Identify the configuration file you want to retrieve (the one currently in use) located in C:\Rolta\OnPoint6.x\OnPointWebsite\WEB\Config\ConfigFiles.
2. With the name of the configuration file identified (ex. OnPointConfig_69f1719c-468f-425e-9ddc-48e08e2cf692.config) browse to the Backup folder located at C:\Rolta\OnPoint6.x\OnPointWebsite\WEB\Config\ConfigFiles\Backup.
3. Find all the configuration files with the same filename as the one identified in the previous step, with extra information appended to the end of the filename (ex. OnPointConfig_69f1719c-468f-425e-9ddc-48e08e2cf692.config_[2007-Aug-30-3-28-50].bak). The extra information at the end indicates the timestamp of when the backup was taken. The format is [YYYY-MM-DD-hh-mm-ss].
4. At this point, using the timestamps choose the backup that will revert you back to a proper working state. Once you have decided on a backup configuration file, copy the file to your ConfigFiles folder (with the extra information and *.bak extension intact).
5. Now you can proceed to delete the previous configuration file that was in the ConfigFiles folder or if you had no configuration file, rename the one you just copied over in the previous step. You will have to take out everything after the *.config (i.e. _[YYYY-MM-DD-hh-mm-ss].bak).
6. You can now start your admin tool and use the Manage Instance Configurations Tool to point to your backup configuration file. You may have to perform a restart on the admin tool for the changes to fully take effect.

Note 1: C:\ is where OnPoint is installed. Please browse to the location where OnPoint is installed.
Note 2: OnPointWebsite is the instance we are working on. Please change this to the default instance you are working on.

If you wish to change the timeout in OnPoint 6 you will have to make the change in two different locations; three if you have security enabled. The first place would be in the web.config file that can be found in the web folder of the instance that you wish to increase the timeout for. Open the web.config file and do a search for the word sessionState. You will then want to change this value from 20 to whatever time you wish to make it.

The second place you will have to change the timeout is in the IIS settings. You will have to migrate to the virtual directory that the OnPoint web site is running in; by default it is called OnPointWebsite. You will have to right click on the virtual directory and select the virtual directory tab and then the configuration button. This will open up a new window titled application configuration and you will want to select the options tab. You will then want to increase the session timeout to the same number you set in the web.config.
Restart your IIS for the changes to take effect.

If you have security enabled there is one more place in IIS that will need to be changed. This relates to the cookie timeout. You will have to navigate to the OnPointWebite virtual directoryin IIS. You will have to right click on the virtual directory, go to properties and select the ASP.NET tab and then the edit configuration button. Once in the new pop up window you will want to select the authentication tab and change the cookie timeout to more the 10 minutes. You will then also want to select the state management tab and increase the session timeout to the same minute value.
Restart your IIS for the changes to take effect.

1. Identify the configuration file you want to retrieve (the one currently in use) located in C:\Rolta\OnPoint6.x\OnPointWebsite\WEB\Config\ConfigFiles.
2. Copy the configuration file. (i.e. OnPointConfig_8cb9cf31-488b-4413-bc90-6ad1b1226b43.config)
3. Paste the configuration file in the newly created instances' ConfigFiles folder. (i.e. C:\Rolta\OnPoint6.x\NewInstance\WEB\Config\ConfigFiles)
4. In the NGConfigFiles.xml located in C:\Rolta\OnPoint6.x\NewInstance\WEB\Config add the following before the "CONFIG_FILES" tag:
5. You can now start your admin tool and use the Manage Instance Configurations Tool to select the new configuration file.

Note 1: C:\ is where OnPoint is installed. Please browse to the location where OnPoint is installed.
Note 2: OnPointWebsite is the instance we are working on. Please change this to the default instance you are working on.
Note 3: If transferring the configuration file between servers the server name needs to be changed manually in the .config file; only if the server name was used and not localhost.

In the legend.aspx (C:\Orion\OnPoint6.x\OnPointWebsite\WEB\WebPages\Map) you will need to change the following (the items in bold):

Please note localhost should be changed to your server name and the legend image (ex. FC-Legend.jpg) should be placed in a web shareable location.