Page Comparison

This chapter guides you through the installation process of the Digizuite™ DAM Center. 

In order to install the Digizuite™ DAM Center, you need to run the provided .exe file named DigiZuiteDamCenter_Setup.exe.

The installer is split into six main steps:

• Basic configuration
• Database connection
• IIS configuration
• System configuration
• Storage configuration
• License

2.1 Welcome screen

End-User License Agreement – that makes you aware of what you are going to install. In order to proceed further on with your installation, you have to accept the terms in the End-User License Agreement.

• In order to continue, read and understand the text and wing off the checkbox to accept the terms. Afterward, press Install to continue

The DAM Center installer will first check for it's requirements, such as specific IIS features or the .NET Framework. If it is unable to automatically set up these requirements, the user will be prompted to take action.

Once the requirements are met, another installer for the DAM Center is launched. To proceed, press Next.

The above EULA is the same as in the first window. You must agree to it as well to proceed.

2.2 Basic configuration

To setup your Digizuite DAM Center, you have to fill out the following fields correctly:

• Protocol – choose between HTTP and HTTPS

  Note
  title Note
  It is recommended to use port 443 if using HTTPS.

  
  

• Sitename – insert desired site name for your DAM Center. Example: digizuite.mycompany.com
• Port – is by default set to 80 for HTTP (for HTTPS, use port 443)

• DamCenter Database Name – you may choose the database name for your DAM Center installation.

  Note
  title Note
  The database name must end with "_dam" (E.g. digizuite_dam) The database name MUST NOT start with numbers

  
  

• LogFiles Rootfolder – by default set to "C:\LogFiles\".
  

• Install DAM for Sitecore – if you have purchased a DAM for Sitecore license as well, check the box to prepare the DAM Center for Sitecore

In order to continue to the next step, you will have to press the Next button.

2.3 Database Connection

To connect to your database, please fill in the following fields:

• Server Name – insert the SQL server name
• Instance Name – (Optional) insert the instance name (only fill out if you have multiple SQL servers on the same machine or if you have multiple instances in the same SQL version)
• Authentication – choose one of two ways of authenticating
  • Windows Authentication – using the Active Directory credentials
  • SQL Server Authentication – using the SQL Server credentials
    • Username – insert the username for the chosen authentication procedure
    • Password – insert the password corresponding to the selected username

You can verify the database connection by pressing the Verify button. If the connection was successful the following message will pop-up.

In order to continue to the next step, you will have to press the Next button. (Pressing Next will also test the connection to the database)

2.3 IIS Information

• IIS user – insert the name of the IIS user (e.g. digibatch, or administrator)
• IIS domain – insert the domain or machine name.
  • You may use machine name instead. Do not ever use . as a replacement for the machine name - it will result in an error stating that the "logon as a service" isn't enabled for your user.
• IIS password – insert the corresponding password to the selected user
• IIS Site Folder – the installer will automatically fill in the path for you. If the selected path does not fit your solution, you can change it by pressing the Browse button
• LogFIles RootFolder - this path is also filled out by default.

In order to continue to the next step, you will have to press the Next button.

Note: if the information supplied is not correct, a warning message will pop-up.

2.4 System Information

• System user – Write in the username of the "digibatch" user created in the previous guide.
• System user domain – If the user is a domain user, you change this to be the same as the user above's domain.
• System user password – insert the user's password

• Storage folder – the installer will automatically assign a folder for the storage. 

  Warning
  title Important
  You're most likely making an installation with multiple machines connected to it. In that case, it's very important that you change the storage path to a share, else the batch machine will not be able to receive any files for processing. E.g. \\yourWebMachine\Storage

  
  

• DigiMonitor Folder – the installer will automatically assign a folder for the DigiMonitors plugins. You can change the path by pressing the Browse button

In order to continue to the next step, you will have to press the Next button.

2.5 Storage Information

Figure 8 – Storage configuration

• Storage stream user – Insert the username for the storage area as created in (usually named assetstream)

• Storage stream domain – Insert the domain or the machine name like in an earlier step. Use the domain name if you are using a domain user and machine name if you don't.

• Storage stream password – The user's password

In order to continue to the next step, you will have to press the Next button.

2.6 Solr Information

To use DAM Center with a SolR installation, this page must be configured. If you do not need Solr, or wish to configure it later, please check Solr Disabled and click Next.

• Solr Server API Url – the full URL to the Solr API (e.g. http://192.168.1.10:8983/solr)
• Solr Unc Path – The absolute UNC path to the SolrService directory (e.g. \\SolrMachineHostname\SolrService)
• Solr Unc User –The username of the UNC user to be used with Solr (e.g. SolrUser)
  
• Solr Unc Domain – The domain for the Solr user to log in with (e.g. CompanyDomain)
  
• Solr Unc Password  – The password corresponding to the Solr user.
  

2.7 SMTP Information

2.6 License Activation

Together with the provided installer, you will receive the necessary license information to activate the Digizuite™ DAM Center in a license document. Insert this information into the following fields:

• Serial number – paste the key from the license document (*Required)
• License Holder Name – paste the license name from the license document (*Required)
• License Key for Digizuite product - paste the key from the license document
• License Key for Assets - paste the key from the license document
• License Key for Users - paste the key from the license document
• License Key for Metadata languages - paste the key from the license document

In order to continue to the next step, you will have to press the Next button.

2.7 Choose Setup type

There are two options available for installing the Digizuite™ DAM Center:

• Typical – installs the main program features. This is recommended for non-advanced users
• Custom – enables the user to choose which features should be installed and where they should be installed. This is recommended for advanced users

2.8 Custom Setup – advanced

The Custom Setup enables you to select the different features to be installed together with the DAM Center. By clicking on the name of each feature, the installer will provide information regarding the size of the installation as well as details about how the plugin can improve your working system.

In addition to providing information, you can change the installation destination of the feature.

Note: the above window will show up only if you select the Custom setup in subchapter 2.7 Choose Setup type. (x)

2.9 Ready to install

Click Install to start the installation using the provided information.

2.10 Installing dialog

You can keep track of the installation process by following the Logs window.

Close the IIS window if it's open, as it'll make the installation take longer.

The installer will change to the following screen when the process is finished. In order to exit the Setup Wizard, press the Finish button.

Once that window closes, you may also close the original installer window by clicking Close.

In order to verify that the installation was successful, open any installed browser and go to the DAM URL chosen during the installation. The following window should be now available to you: