SetUp PRO.FILE

Connecting PRO.FILE takes three steps. The first one belongs to whoever maintains your PRO.FILE installation. Nothing else can be done until that is in place.

Prerequisites

Your PRO.FILE maintainer needs to set all of this up

  • A PRO.FILE service account for amber, with a license assigned (normally full-use). Without one the account looks fine in the desktop client but cannot sign in to the interface amber uses.

  • Sign-in permitted, with a username and password set in PRO.FILE

  • IIS Basic Authentication switched off on the site hosting the AppServer.

  • Network access to the AppServer address and port.

Amber indexes only what the service account can see, and each user still sees only the documents their own PRO.FILE permissions allow.

1. Prepare PRO.FILE and the AppServer

1.1. Create the service account

Create a PRO.FILE account for amber:

  • A license assigned to the account (normally full-use).

  • Sign-in permitted, with a username and password set in PRO.FILE.

1.2. Switch off IIS Basic Authentication

The PRO.FILE AppServer runs on IIS. On the IIS site hosting it, open Authentication and set:

  • Anonymous Authentication — Enabled

  • Basic Authentication — Disabled

The IIS Authentication panel for the PRO.FILE AppServer site, with Anonymous Authentication set to Enabled and Basic Authentication set to Disabled. Forms Authentication and Windows Authentication are Enabled, ASP.NET Impersonation is Disabled.

IIS Manager → the AppServer site → Authentication. The two rows that matter are arrowed: Anonymous Authentication: Enabled and Basic Authentication: Disabled. Leave the other rows as they are.

1.3. Optional: Open documents in PRO.FILE

Amber offers an Open in PRO.FILE action that opens a document in the desktop client. To enable it, send amber your SmartLink target as well. Your PRO.FILE maintainer has the exact value, which looks like server-name/db(tenant).

2. Collect the connection details

Four values, all of which your PRO.FILE maintainer can confirm:

Server address

The AppServer address, including the port — for example http://profile-server:83. Just the server root, not a longer path.

Tenant

The AppServer address, including the port — for example http://profile-server:83. Just the server root, not a longer path.

Username

The service account’s name, exactly as it appears in PRO.FILE.

Password

The service account’s PRO.FILE password.

3. Share the details with amber

Securely share the server address, tenant, username and password with the amber support team.