On-Premises Installation: Instructions
This section provides instructions on how to install ConceptShare on a single-server instance (all services on the same box).
Installation Checklist
A. Download the Installer
- Launch Internet Explorer and go to https://dsm.deltek.com/dsm.htm.
- On the Deltek Software Manager web page, click Run Deltek Software Manager.
- In the Deltek Software Manager logon dialog box, enter your Deltek Customer Care User ID and Password, and click Logon.
- To select the folder where you want to download the installer file, click
Settings at the top right corner of the Deltek Software Manager.
Note: When you log on for the first time, DSM asks you to select a default folder where Deltek products are to be saved.
- Use the Settings dialog box to specify the folder where you want to download Deltek products, and click OK.
- In the left pane, expand the ConceptShare folder and select the product type that you want to download.
- In the table, select the checkbox that corresponds to the version that you want to download. The right pane displays a message stating that the product has been added to the download queue.
Note: To view the items in the download queue, click View Download Queue at the bottom of the left pane.
- Click Download at the bottom of the left pane. The Deltek Software Manager downloads the installer file to the folder that you selected.
B. Extract and Configure the Installer
- Extract the install client on the ConceptShare server to a desired location. (This procedure will assume C:\InstallClient.)
- Copy your license file (.LIC) to the Licenses folder C:\InstallClient\Licenses.
- Launch the installer C:\InstallClient\ConceptShare.V4.Installer.exe .
- In the ConceptShare Installer wizard, select Configure Settings, and then click Change.
- On the Installation Settings page, specify the information for your environment. Pay particular attention to the following fields:
Field Description Instance Administrator Set the name, email, and password for the user who will be the "super user" for the ConceptShare installation. Remember these credentials as they will be used later on to create your first ConceptShare account. Database Database credentials are what the application components will use to access the database. - If you are using Windows Authentication, it should be noted that the Queue Windows Service and IIS Application Pool MUST run under credentials that have access to the SQL database. In this scenario just set the "Database – Authenticate Type" to "Windows"; the other two settings (SQL Username/Password) will be ignored.
- If you are using SQL authentication, set the username and password that you would like to use.
Database The remaining database settings are the name of the ConceptShare database to be created, and the server location (which, for this deployment scenario, is "localhost"). If you have a named instance, be sure to include it here (that is, localhost/ConceptShare). Location The location settings are where the data files should be stored. By default, all data is stored in C:\ConceptShare. If you would like to store data on a different drive or even a network location, you would specify them here. For example, Location – Data Directory could be: \\192.168.1.2\CSData\Assets. Note: The ConceptShare Queue windows service and the application pool within IIS must use credentials that have access to these locations. In addition, the DB location must also be writable by the SQL Server identity.Queue Service These settings determine the name of the Windows Service for the ConceptShare Queue as well as the identity to run under. In a single-server deployment scenario where all data resides on the same server, Local System identity is typically sufficient. If you are using a custom user identity, change "LocalSystem" to "User" and specify the credentials in the settings. - Click
Save and return to the main installation screen.
Note: Settings are stored in your license file (LIC).
C. Install and Configure the ConceptShare Database
- On the main ConceptShare Installer window, select Manage Database, and then click Manage.
- On the Install Database page, the settings are pre-populated with the credentials from your installer settings. These settings will be used during this step, so there is an option to test the settings to ensure that they work. Click Test Connection to make sure that the settings are valid. If not, adjust your settings accordingly.
- Perform the pre-flight configuration. This should only be performed once per installation of an instance.
This step restores a template database to SQL server and ensures that the .NET CLR is enabled.
- If required, perform the following steps for a single-server deployment within the installer:
Option Steps To use the installer to do the leg-work: - Select Perform Pre-flight Configuration, and then click Run Scripts.
- Once pre-flight is complete, a template database should have been restored to the SQL server and .NET CLR enabled.
If an error occurred, it usually has to do with the level of credentials used. For example, enabling the CLR typically requires a sysadmin role.
To perform the steps manually: If you have a deployment configuration where the SQL server instance is on a separate machine, or if you want to review and perform these steps manually (for instance, by your Database Administrator)
- Clear all pre-flight options except
Restore Template Database.
This will generate the scripts that the installer will perform using your supplied credentials. At this point, you can review the script and, if acceptable, just have the installer run it. However, in the case where the SQL Server is on a different machine, you must copy some data and change some of the script as noted in the following step.
- Copy the database template file C:\InstallClient\Data\DB\BASE.BAK to the SQL Server where you want it placed. This procedure assumes you saved it to C:\CS_DB.
- The default restore script will look something like the following example. Since the locations are different on your SQL Server, you must change the restore file location and the move locations for the database files. The following is an altered sample script using a typical database path for SQL Server. Yours may vary.
Original
RESTORE DATABASE [conceptshare] FROM DISK='C:\InstallClient\Data\DB\BASE.BAK' WITH REPLACE, MEDIAPASSWORD=N'715C0EDE-1E73-4025-94D2-5E8015C18D8B', MOVE 'conceptshareV4_base' TO 'C:\ConceptShare\DB\conceptshare.mdf', MOVE 'conceptshareV4_base_log' TO 'C:\ConceptShare\DB\conceptshare.ldf' GO
ModifiedRESTORE DATABASE [conceptshare] FROM DISK='C:\CS_DB\BASE.BAK' WITH REPLACE, MEDIAPASSWORD=N'715C0EDE-1E73-4025-94D2-5E8015C18D8B', MOVE 'conceptshareV4_base' TO 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data\conceptshare.mdf', MOVE 'conceptshareV4_base_log' TO 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data\conceptshare.ldf', GO
- Once you have replaced the restore step with your appropriate locations and successfully executed the restore step on the SQL Server, you can either perform the remaining pre-flight steps manually or use the installer. Clear Restore Template Database and select all the remaining pre-flight options. If you are having the installer do these steps, click Run Scripts; otherwise, preview the scripts, copy, review, and execute them on your SQL Server instance.
Regardless of deployment method (separate server, single server), the pre-flight steps should now be completed.
- Now that the template database is restored, you need to stamp your particular license details into the database.
On the main ConceptShare Installer window, select Initialize Database, and then click Initialize.
If the pre-flight steps were completed successfully, this step should return with a message stating that everything was successfully initialized.
Note: This step does NOT affect any data. No data (other than contractual details) is changed or modified at this time. Your assets, commenting, and other data will remain intact.
At this point, the database is installed, configured, and ready for use.
D. Install and Configure the File System
- On the main ConceptShare Installer window, select Initialize File System, and then click Install.
- Ensure the base path is correct where the location of your data files is, and then click
Deploy.
The installer will copy the data files to their specified locations for use with ConceptShare.
E. Install and Configure the Queue Service
ConceptShare uses a windows service for processing files, event management, email processing, and so on. This procedure will install that service. All settings are pulled from the Installer settings, including the credentials to be used.
- On the main ConceptShare Installer window, select Manage ConceptShare Queue Server, and then click Manage.
- Since this is a new installation, the first (pre-selected) option is what you want to do. Click
Install to create the windows service and copy the appropriate queue files to the queue application folder and generate the appropriate configuration file.
Note: You must have sufficient credentials to create a windows service.
Once complete, the windows service should be visible via the Services snap-in under Administrative Tools within Windows. If appropriate credentials were given, the windows service should also be able to start.
F. Install and Configure the Website (IIS7)
- On the main ConceptShare Installer window, select Manage ConceptShare Website. Make sure the path selected is the desired location for the website files.
- Click
Deploy.
This installs the required files and sets up the appropriate settings in the web.config file.
Attention: If you are using installers version 6.32 or later, you need to manually add the following app setting in the web.config file of your ConceptShare website to avoid errors or blank CS:<appSettings> <add key="CS.VideoUploadSizeLimitInBytes" value="2147483648" /> <add key="Database.Command.Timeout" value="30" /> </appSettings>
- Open the IIS snap-in and navigate to Application Pools.
- On the right-hand side, click Add Application Pool.
- In the Add Application Pool dialog box, specify this information:
Field Description Name Specify ConceptShare. .NET CLR version Select NET Framework v4.0.30319. Managed pipeline mode Select Integrated. Start application immediately Use the default selection (selected). - Once it is created, select it from the list, and then click Advanced Settings on the right-hand side.
- Change the following settings:
Note: You can configure additional settings as required.
Field Description Enable 32-Bit Applications Select True. Identity Set to an identity with sufficient privileges to access files. If all files reside on the system and you do not want to use a custom account, you can choose LocalSystem. Note: These credentials must also have access to the SQL database if you choose Windows Authentication for the application user credentials.Load User Profile Select True. - If ConceptShare is the only website being hosted on the web server, you can delete the Default Web Site.
- Within IIS, right-click the Sites node, and then select Add Web Site.
- In the dialog box, specify the following information:
Field Description Site Name Specify ConceptShare. Application Pool Select the ConceptShare application pool you created in steps 3–4. Path The physical path should point to the location where you selected ConceptShare website files to reside: C:\ConceptShare\website IP address If you have to bind ConceptShare to a specific IP address, restrict to a specific hostname, or apply SSL, you would do so at this stage. Generally, most deployments leave IP unassigned and hostname blank. Note: Self-signed certificates are not compatible with ConceptShare when uploading via the User-Interface.API For the ConceptShare API to work properly, you can only have one HTTP and one HTTPS binding per website. Multiple HTTP/HTTPS bindings will cause the API to fail. - Click
OK to create the website.
At this point, the website should be set up within IIS. Highlight the website from within IIS, and on the right, there should be an option to Browse the website. If everything is successful when you attempt to browse the website, you should be redirected to www.conceptshare.com. The reason for this is that you do not have an account configured in ConceptShare for this domain.
G. Configure the Instance Settings
This procedure assumes that your website is resolvable via localhost.
- Navigate to the administration panel: http://localhost/AdminPanel.
- On the Login screen, use the credentials for the instance administrator that you configured in your installer settings.
- On the Administration Panel page, click the Instance Settings tab, and then pay particular attention to the following settings:
Setting Description Email Settings This is where you should fill out your SMTP settings so that emails generated by ConceptShare can be sent. Location Settings This section indicates the various paths where ConceptShare will locate files. Most of these paths should be accessible by all ConceptShare servers by using a central location. Important: This section is CRITICAL and must be set properly for ConceptShare to work.Maintenance Settings This section is used to determine the data retention policies of ConceptShare data.
H. Configure Your First ConceptShare Account
This procedure assumes that your website is resolvable via localhost.
- Navigate to the Administration panel by going to http://localhost/AdminPanel.
- On the Login screen, use the credentials for the instance administrator that you configured in your installer settings.
- On the Administration Panel page, click the Accounts tab, and then click New Account.
- In the Add Account dialog box, specify the following information:
Field Description Is Active Select the checkbox. Owner Email Enter the email address of the instance administrator. Account Name Enter the name of your ConceptShare account. Domain This is the domain in which people will access ConceptShare. This domain displays in emails regardless if other aliases are used. An example domain would be: conceptshare.yourcompany.com/. Header Text This is the text that will be displayed in the header bar or title of the browser window. Typically, this is the same as the account name. Package Typically, you only have one package choice. In case your contract specifies multiple choices, select the appropriate package. User Limit This is the number of users to assign to the account. Most installations only have one account so you can assign all the users in your contract to this account. Storage/Storage Per User This field will determine the amount of storage available to the ConceptShare account. It is a good idea to leave a buffer in terms of space versus actual physical storage so that the system does not halt due to lack of space. Also, ConceptShare only calculates storage based on actual assets and their proxies and does not include temporary files, system files, and supporting files (thumbnails, page extractions, and so on). As a general rule, if you take 50% of your total storage and make that your ConceptShare limit, you should be safe. The difference between Storage and Storage per User is that Storage is a fixed total amount regardless of user count. In Storage per User, you assign storage based on the number of users in an account. For example, if you want to assign 1 GB for every user, you would put that in Storage Per User. Note: There is a storage calculator to the right as the text boxes require storage amounts to be in bytes. - Click
Save and click
Search.
The account should be listed. If you click the Primary Domain field, you should be either presented with the ConceptShare login screen or, in the case where the primary domain is the current domain you are on, that is, a localhost, you should be auto-logged in.