Applicable versions: 6.0

Version 6.0 has introduced new measures to secure communications to the DataPA Enterprise Service, and as a result, the means of configuring an alternative port for the Enterprise Service has changed from previous versions.

First, if you are currently using a DataPA Enterprise Service as your data location in DataPA, you need to temporarily change this to read from the local disk rather than from the service . Open the Client Settings, set to "Stored as static files..." and use the default data location.

Now stop the Enterprise Service.

There is an optional configuration file that should reside in <install drive>:\ProgramData\DataPA (this is a hidden folder), named enterprise.cfg.  

If enterprise.cfg does not already exist, create a new text file with this name.  It's contents are a few simple properties represented in the JSON format.

To specify an alternative port for the Enterprise service, the contents of the file should be at minimum:

{

     ServiceEndpoint: "http://localhost:81/DataPAServiceModel/EnterpriseService"

}

If the enterprise.cfg already exists, you may have other properties set in it, in which case it may look something like this:

{

     UseAnonymousAccess: true,

     TokenEndpoint: "http://mysite.com/datapaenterprisespa/token",

     ServiceEndpoint: "http://localhost:81/DataPAServiceModel/EnterpriseService"

}

If you are using SSL (HTTPS) on your server, change the above URLs to begin with "https://".

Now start the DataPA Enterprise Service, and then restart the DataPA Application Pool via the IIS Manager, which you can access via the Control Panel in Windows under Administrative Tools.

Back in the Dashboard Designer application's Client Settings, change the data location back to the Enterprise Server, now running on a different port. For example, if running on port 81 on my own computer, I would enter the connection as localhost:81 as shown below:

DataPA should now run using the port you have specified.