Chat now with support
Chat with Support

Metalogix Archive Manager for Files 8.1.1 - Advanced Installation Guide

Cluster installation

If Archive Manager for Files is to be installed on a cluster, it has to be installed on all nodes of the cluster regardless Active/Active or Active/Passive cluster environment. All installations have to be configured to use the same archive (store) and the same database. (See the following picture.)

NOTE: When updating Archive Manager for Files installed on a cluster, it has to be updated on all cluster nodes.
configuration

Installation steps:

1.Create a common Archive Manager database.

2.Create a common archive (store) to be used (in our case it is HSM).

3.Install Archive Manager for Files on all cluster nodes.

4.Configure all installations to use the same archive and database (see the next section of the manual).

Configuring Archive Manager for Files

When installation of Archive Manager for Files is finished (see the previous section), simply continue with configuration. Archive Manager requires connection information to the database, so please enter the requested data as described below.

NOTE: In the Configuration tool you can see also other our products, if they are installed on your machine. However, for Archive Manager for Files you need to configure just the Files Archive part.

To configure Archive Manager for Files, follow these steps:

1.In the initial Configuration window select the Files Archive tab in the left pane. (By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.)
a-PAM tab

2.Click the Configure button to start the Database Connection Wizard and update the configuration settings.
b-empty

3.In the case that you are working with an MS SQL database, select the Microsoft SQL Server option and then click Next.

NOTE: For an Oracle database select the Oracle option.
c-SQL

4.On the next page please enter the requested data:

·If you have selected Microsoft SQL Server in the previous window, fill in these fields:
Server name (the name of your MS SQL server)
Initial catalog (the name of the database for Archive Manager)
Table owner (the owner of the table or schema)
Authentication (authentication type used for the database)
User name (the database login name)
Password (enter the requested password)
d-SQL connection

·If you have selected ORACLE in the previous window, fill in these fields:
ORACLE NET Name (ORACLE NET name, TNS name)
Schema (the name of the schema where Archive Manager tables will be created)
User name (log-on user for the database with read and write rights to the table)
Password (log-on user’s password)

Afterwards, click Next.
e-oracle

5.Click the Finish button. Next, you will have to execute the database scripts.

6.Back in the Configuration window on the Files Archive tab the data you have entered are now filled in. Run the scripts by clicking the Execute scripts button in the Scripts section.
g-scripts1

7.In the following window click Select All button or select the scripts one by one. It is necessary to select and run all scripts. Then click Next.
g-scripts2

8.In case of SQL server authentication, in the Database user text field enter the database user under which the scripts will be executed. Enter the password in the Password field, if needed. Click Next.

NOTE: To see the scripts, check the I want to see the SQL scripts before execution check box. On the following page you can read the scripts as well as save them.
g-scripts3

9.Click Next to execute scripts.

10.When the process has finished and all scripts were executed successfully (indicated by the green sign), click Finish.
g-scripts4

11.Successful execution of scripts will be indicated in the Scripts section of the Files Archive tab where you can read the bottom line message: “Your database is up to date.”
g-scripts5

12.On the Search options tab you can enable Exalead support, if you wish. (For more information see the “HOW TO – Exalead fulltext installation and configuration” manual.) Then close the Configuration window.
i-options

13.The Archive options tab by default does not need to be changed. It is filled in by default and configuration is necessary only for special purposes (e.g. changing the HSM server). It contains the following information:

Machine name – name of the machine where Archive Manager for Files is installed

HSM server – indicates the HSM server

Minimum size of the – identifies the minimum size of a file, which can be replaced with a shortcut after archiving
i-options2

Installation of Archive Manager for Files is completed. Click Finish and you may start using Enterprise Manager.
 

Addendum

 

·Remote HSM Server

·Troubleeshooting: Adobe reader X is not able to open archived PDFs

 

Remote HSM Server

In case of a remote HSM Server, i.e. if the HSM Server is installed on a separate machine, it is necessary that:

·The HSM Base service runs under the Archive Manager super-user account

·DCOM Rights are reduced

a)The Archive Manager super-user account is an account under which Archive Manager services (MAMfsaHandlerSv, MAMfsaRemoteSV, MAMfsaArchiverSv) run on the Archive Manager server.

On the HSM server, follow these steps:

1.Open Start / Administrative tools / Services and locate the MAM HSM Base Operations service.

2.Right-click it and open its Properties. On the Log On tab check This account option and enter the super-user account with its password. (Super-user account is an account which Archive Manager services (MAMfsaHandlerSv, MAMfsaRemoteSV, MAMfsaArchiverSv) run under.)

Finally click OK.
0-HSM base

b)DCOM Rights has to be reduced in two locations to

·AuthenticationLevel=“None”

·ImpersonationLevel=“Anonymous”

 

and after that the IIS have to be reset.

 

On the HSM Server follow these steps:

1.Open machine.config from:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config
In case the 64-bit .NET FrameWork open:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config

2.Locate the entry for “processModel” and add:

comAuthenticationLevel="None" comImpersonationLevel="Anonymous"

The entry then looks as follows:

<processModel autoConfig="true" comAuthenticationLevel="None" comImpersonationLevel="Anonymous" /> 

3.Close the config.

4.Now run Component Services (click Start /Settings /Control Panel /Administrative Tools /Component Services).

5.In the Component Services window expand the Component Services tree down to Component Services \Computers \My Computer and then right-click My Computer to open its Properties window.

6.Switch over to the Default permissions tab. Check Enable Distributed COM on this computer. Then in the Default Authentication Level dropdown box select None and in the Default Impersonation Level select Anonymous.
Click Apply, then OK.
0-remote HSM

7.Finally reset IIS.

Related Documents