Configure The Server – uPerform On-Premise Manuals

When configuring the Server, pre-defined users are created:

The Admin user is the system administrator account used when initially logging into the Server. This user is assigned the default password "admin." The Server will prompt to change this password after a new installation. This account can be used and modified.
The uPerformSystem user is used by internal components to communicate with the content management system (CMS). It is recommended that you do not modify or delete this user. This account should only be used by support personnel. The uPerformSystem default email address is uPerformSystem@ancile.com. If this email is being seen as spam, the email address can be configured to an email address more relevant to your organization. Refer to: Configuring the uPerformSystem User Email Address.
The SolutionManager user is created for integration with SAP Solution Manager. For more information, refer to Integrating SAP Solution Manager.

NOTE:

The uPerformSystem and SolutionManager passwords are changed automatically to a randomly generated password.

Configuring the Server After Installation or Upgrade

Open Internet Explorer.
Enter the server URL in the format http://[Server Name] and login to the server as the admin user to confirm a successful configuration.

NOTE:

If you are using a port other than the default port 80 for IIS, you must enter the server URL in the format http://[Server Name]:[IIS port number].
Click Start.
If prompted, enter a new password for the administrator.
Enter an email address for the administrator.
Select a time zone from the Time Zone drop-down list.

Perform one of the following options:

If You Want To	Then
Configure the server for an upgrade from a pre- 4.x version	Enter the field mapping for your Directory Server. Click Save.
Configure the server for a new installation or upgrade from a 4.x version	Click Save.

NOTE:

Automated tasks will now run to complete the installation. Allow these processes to complete before continuing.

If you want to go to the server, click Go to my server.

Turning On the READ_ COMMITTED_SNAPSHOT Command

If you are installing the Server on an SQL Server, the application will run a check during installation to ensure the READ_COMMITTED_SNAPSHOT command is turned on. If the command is not turned on, you will receive a prompt during installation. You can continue to run the installation but you must turn on the command once the installation is complete.

If you have a large number of concurrent users, the READ_COMMITTED_SNAPSHOT command helps to provide your users with uninterrupted access to the Server from the Editor or a web browser. This setting reduces locking contention for data during periods of high activity. This setting is required to ensure the successful execution of background jobs on the application server. For more information about Snapshot, view the detailed Microsoft Technical Article at: http://msdn2.microsoft.com/en-us/library/ms345124.aspx.

Stop the Collaboration service on the application server.
If you originally installed the application using a 1.XX version, you will need to run bin/stoprmid.bat from the Collaboration directory.
Ensure that no open connections exist with the database.
Log into the SQL database as an administrator.
Select New Query.
Enter the following command:
ALTER DATABASE [collabdatabase] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

GO

ALTER DATABASE [collabdatabase] SET READ_COMMITTED_SNAPSHOT ON;

GO

ALTER DATABASE [collabdatabase] SET MULTI_USER;

GO

SELECT is_read_committed_snapshot_on FROM sys.databases WHERE NAME = '[collabdatabase]';

GO

NOTE:

[collabdatabase] is the name of the Collaboration database.
Click Execute.
Verify the results return one row displaying 1, which verifies that the snapshot command is turned on.
Start the Collaboration service.
Verify that the service is running by accessing your server through the web interface.