Install iMIS

• Multiple versions of iMIS can be installed on a single machine.
• Users can install a newer version while retaining an older version of iMIS on a machine.
• The application pools can be named by users. The iMIS installer also allows for multiple application pools. This allows older versions using a 32-bit application pool to run concurrently on systems where newer versions require 64-bit application pools.

Note: New application pools are set to 64-bit mode by default. Users must set application pools to 32-bit if they want to run 32-bit operations.

• Allows for up to 25 instances of iMIS to be installed on a single host.
• Only one instance of com files is installed. This instance will be used for all desktop installs. Because only one instance of com files can be registered, subsequent installs of later com versions might not be compatible with older versions of iMIS (desktop client only).

Note: Versions 15.2.5.3815 and earlier are not compatible with the latest com components.

• When installing on a system where iMIS uses the default web site, the installer will force an upgrade of the existing installation. After the existing installation is upgraded, additional instances can be installed.
• Modify and Repair options are not available when performing maintenance on installed instances.

Do the following to download the product:

1. Log on to the Support site.
2. Go to Releases > iMIS.
3. Select the most recent version of iMIS and download the associated self-extracting zip file, for example, iMIS nn.n.n.n_Production_GA.zip.
4. Select the most recent update to the release, if any, and download the zip file.
5. Double-click the downloaded files to extract the files to their default locations on the C: drive.

Note: Review the README file that is included with the Production Release self-extracting zip file.

Do the following to use product images across the network:

1. Copy the extracted product image to a shared network location.
2. On the machine where you will run setup.exe, map a drive letter to the network location of the extracted product image.
3. Browse to the installation program on that mapped drive.

Do the following to install iMIS:

1. Finish all tasks in Prepare all servers and workstations and review the System Requirements.
2. If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, copy and save the existing directory. This will preserve files that are unique to your web site (for example, images, uploads, and so forth).
3. On your application server host, temporarily disable tools and settings that might interfere with the installation:
   • Disable anti-virus software.
4. If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, delete the following:
   • Virtual directory.
   • The ASI Scheduler associated with the site.
   • The ASI Scheduler directory on the file system.

   Note: You must shut the Internet Information Services utility down before deleting the ASI Scheduler directory.

   • The install directory.
5. Run the product setup.exe.

Note: You can install a new instance, or upgrade an existing instance. If an instance exists that is at the same release level as the installer, the installer will open to a welcome page that displays the available instances. You can choose to upgrade or maintain an instance. However, if an instance exists that is not at least at the same release level as the installer, the installer will display an upgrade window. You cannot perform maintenance tasks on an existing instance of iMIS if the instance is at a release-level older than the iMIS installer. For more information about upgrading an existing non-current instance of iMIS, see Upgrading an existing non-current instance of iMIS.

6. Select Install New Instance and click Next.
7. A message indicating that a new instance of iMIS will be installed on your computer is displayed. Click Next.
8. The Destination Folder page is displayed. Each instance will be installed into a different folder.
9. Click Change to change the Destination Folder.

Warning!  

If the Destination Folder has an install of iMIS, the current install will fail and the installed instance will be unusable after the install!

10. Click Next to accept the installation path.

Note: If the directory into which you are installing the new instance already exists, you will see a message asking you if it is OK to continue.
Click Yes. The install will continue, and iMIS will install to this installation path.
Click No. You will be returned to the dialog screen which will allow you to change the installation path.

If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, install to the same directory path that was used with the Multi-Instance Utility.

Warning!  

If the Destination Folder has an install of iMIS, the current install will fail and the installed instance will be unusable after the install!

11. An iMIS Installation window is displayed. Select Install Application Server or Install Desktop Client.

Note: You must select Install Desktop Client to access the iMIS Advanced Accounting Console and the iMIS Desktop.

12. Click Next. The Database information page for your new instance is displayed.
13. Enter the database connection information:
    1. In the SQL Server name list, select a SQL Server instance or manually enter the SQL Server name.

    Note: Do not use (local) for the SQL Server name.

    2. In Database name, enter a name for your iMIS database. Ensure that the name is valid for your SQL Server configuration. If you are using an existing database, enter the name of that database, and select Use an existing database. Otherwise, name your new database.

    If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, select to use an existing database. Use the database that was associated with the instance when the Multi-Instance Utility was used.

    Note: The Database name is case-sensitive.

    Note: The Database name must begin with a letter. Do not use special characters in the name.

    3. For greatest security, select the Use separate (sa) credentials when creating new database checkbox.
       • In the fields on the right, specify a system administrator account, which the installer will use only temporarily.
       • In the fields to the left, specify values for a new, standalone user account to be created by the sysadmin account. These values will be used in your configuration file for enabling database access (db_owner).
    4. For User name, enter the sysadmin login for the SQL Server instance that is hosting the iMIS database.
    5. For Password, specify the password for the accounts you entered. If left blank, the install fails.

    Note: Special characters in the password can disrupt command-line processing, so use only alphanumeric characters and ! # @, with no spaces. You can use hyphens and underscores after the first character, but avoid all other punctuation and symbols.

    6. Select whether to Create a new database or Use an existing database.
       • If creating a new database, select DemoDB or EmptyDB from the drop-down.

       Note: The DemoDB is pre-configured with sample data. To see iMIS in action, install the DemoDB and publish a Quick Start Site. You can also copy a Quick Start Site and tailor the new site to meet your organization's website needs.

       • If using an existing database, you will see a message after you click Next that asks you to confirm your database upgrade. Click Yes.

       You will always see this message unless you have already upgraded this instance to the current version.

14. Click Next.
15. The Application server information page is displayed. Enter any virtual roots, SMTP server, and other information.
    • The Appserver Virtual Root sets the IIS application name created under the Default Web Sites. If you want an additional external site to be routed to this virtual root, specify the name in the External Domain Name.
    • Accept the Publishing Server Code default. If you install additional publishing services, set them to different letters.

    The Publishing Server Code associates the physical publishing service (running on a web server) with the specific Publish Server record in the database that configures it. Select different letters as needed to avoid colliding with the mapping of other installers. If the wizard detects that the path for the code you selected differs from your install location, it prompts you to change either the install directory or the publishing service code.

    If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, you can elect to use existing or use a new code. If you are not installing to the same path as the original install, do not use the existing code.

    • In the SMTP Server Value field, specify the domain name of your SMTP server.

    Note: An invalid domain name will cause several email notification features to fail until you perform troubleshooting steps.

    • If you elected to install a new database, the New Administrator Password field is displayed. Enter a new Administrator and Manager password.

    Note: The new password must be at least seven alphanumeric characters long, and must contain at least one uppercase letter, one lowercase letter, and one number.

    • Enter an External Domain Name to be applied to the install as another website is optional. If you enter a value of www.mywebsite.com, it will create a new website in IIS that maps website URL requests from this value over to the Default Web Site/<Virtual Root> created from the Appserver Virtual Root.
      • If you have already clicked Next and the value entered for the External Domain Name already exists then the following message will display.
        Select No and the installer will display the dialog box for entering the URL. The URL value can be edited at this time to a value that does not exist.
        Select Yes to ignore the website URL. The install will proceed and the pre-existing website URL will not be altered.
      
      
    • In the Application Pool Name field, enter the name of your application pool. You can enter any name you want. The name must be alphanumeric, and must begin with an alphanumeric character. If this is an existing application pool, the installed iMIS application will share with the other applications using the same named application pool.
16. Click Next. The Desktop Client Information licensing window is displayed. Enter the following license information:
    • iMIS URL
    • iMIS Serial #
    • Licensed To
    • Products
    • Max Users
    • Max Records
    • Expiration
    • Checksum

    You can select Skip licensing to continue, and add this information at a later time.

17. Click Next. A Ready to Install the Program window is displayed.
18. When you are ready to install your new iMIS instance, click Install. The installation process can take several minutes.
19. Click Finish when the installation process is complete.

If you are recreating an iMIS instance that was originally created with the Multi-Instance Utility, copy the saved files (for example, images, uploads, and so forth) from the original install directory to the new install directory.

20. Log in to the Desktop client on the new instance. If you do not log in to the Desktop client on your new instance before installing additional instances, then the URL for the Desktop client will default to the URL of the last instance installed.

21. Navigate to Start > All Programs. Notice that additional instances of iMIS will display multiple ASI folders. The first ASI folder will contain the iMIS Desktop application and the Tools folder of the pre multi-instance version of iMIS. The subsequent ASI folders will display the new additional instances of iMIS that you have installed.

    

Upgrading an existing non-current instance of iMIS

You cannot perform maintenance tasks on an existing instance of iMIS if the instance is at a release-level older than the iMIS installer. You will be forced to upgrade if you try to perform maintenance on an existing instance of iMIS that is an older release-level.

If you have a currently installed iMIS instance that is older than the version of the iMIS installer, do the following to upgrade your iMIS instance:

1. Run the setup.exe file to initiate the installation.
2. If there is at least one instance of iMIS at the same release level as the installer, select Install a new instance.

Note: Although you want to upgrade your existing non-current instance of iMIS, you must select to Install a new instance. This will force the installer past the initial installation screen, which identifies all existing instances that are already at the same release level as the installer. The installer will then display a new selection window, enabling you to select a non-current instance of iMIS for upgrade.

3. An Instance Selector window is displayed. Select the Upgrade Existing radio button.
4. Highlight the non-current instance of iMIS you want to upgrade and click Next.
5. A Ready To Upgrade window is displayed. You can select Display debug information for more information about the instance you are upgrading.

When you’re ready to upgrade, click Install. The process can take several minutes.

When the upgrade process is complete, your currently installed instance of iMIS is now at the same release level of the iMIS installer. You can now install new instances, or maintain existing instances of iMIS.

You must perform this task to enable content authoring workflow to function properly.

Some workflow-related actions are initiated directly by users, such as approving a publishing request in your Content Designer Task List. However, the workflow actions related to managing expired content, such as sending expiration notices or removing content that has expired are managed by a program called ContentWorkflow.exe, which must be manually added to the Windows Task Scheduler on your production iMIS application server.

The Task Scheduler is slightly different on each version of Windows, so adapt the following steps as needed:

1. Create a Basic task in the Task Scheduler Library folder.
   • From Trigger > Daily, create a task to check expired content once per day.
   • From Action > Start a Program, specify ContentWorkflow.exe. This is located in C:\Program Files (x86)\ASI\iMIS\Net\bin\ContentWorkflow.exe by default.
     • Add arguments (optional) is not required.
     • Start in (optional) updates the path where the log file is added. This is located in C:\Program Files (x86)\ASI\iMIS\Net.
2. Find the new task that you created in the Task Scheduler Library folder and modify the following properties:
   • On the General tab, select the option to run regardless of whether you are logged on or not.
   • On the Settings tab:
     1. Select the option that enables the task to be run as soon as possible after a scheduled start is missed.
     2. Select the option that stops the task if it runs longer than a certain duration and specify a value, such as 2 hours.

If you have issues completing this process, consider the following items:

• You must have administrative access to the Windows Task Scheduler and the entire file system on your iMIS application server.
• Your user account on the iMIS application server must have Log on as batch job rights.
• To improve logging speed, make sure that you manually clear workflow.log. If you prefer to automate this task, configure Log4Net to purge its contents each time it is run.

When you install iMIS, several system alert tasks are enabled and set up to display to website users by default. After an install, you should review the system alerts tasks to confirm that you do want these alerts to display to users. The review process will differ depending on whether or not you are licensed for advanced tasks.

If you have the advanced tasks license

You should review the system alerts tasks to confirm that they are configured appropriately for your organization. If you do not want a system alert task to generate an alert that displays to users, you need to disable the task.

1. In the Staff site, go to RiSE > Process automation.
2. Select the Tasks tab.
3. Open and review the alert tasks.
   1. If you do not want to use a system task, deselect Enabled.
   2. Confirm that the task uses an appropriate Conditions data source. The task only runs when the data source returns records.
   3. Confirm that the Alert is configured appropriately.
4. Review the query data sources used as conditions in the enabled tasks. Data sources are located at $/Common/Tasks/Queries in the Document System. If you want to modify a query data source:
   1. Copy the query.
   2. Modify your version of the query.
   3. Update the task to use the new Conditions data source.
5. Go to RiSE > Process automation.
6. Select the Alert sets tab and confirm that the alert tasks are located in the appropriate alert set.

If you do not have the advanced tasks license:

You cannot edit the out-of-the-box alert tasks, but you can control whether or not they display on your website by including or removing them from the system alert sets. If an alert task is not included in an alert set, it does not display.

1. In the Staff site, go to RiSE > Process automation.
2. Select the Alert sets tab.
3. Open the alert set you want to edit.
4. To add an out-of-the-box alert task to the set:
   1. Select Add New.
   2. Select the alert task you want to include from the Task drop-down.
   3. Save the task.
   4. Use the arrows to arrange the alert tasks in the desired order.
5. To remove an out-of-the-box alert task from the set:
   1. Select the alert set.
   2. Choose Delete selected.
   3. Click OK to confirm the deletion.
6. Save the alert set.

See Displaying automated alerts for more information.

If you have more than one instance of iMIS, you might need to configure Advanced Accounting Console to be able to connect to more than one instance, such as connecting to test and production environments.

Note: The URL for the Advanced Accounting Console must end with /CS2.

Configuring Advanced Accounting Console to connect to multiple iMIS server URLs

Do the following to configure Advanced Accounting Console to connect to multiple iMIS server URLs:

1. Open Advanced Accounting Console but do not log on.
2. Click Cancel.
3. From the Advanced Accounting Console menu bar, go to Logon > Set Host Location.
4. On the Local Preferences window, click Insert.
5. On the Application Server URL Setup window, specify one of the iMIS server URLs in the Server field.
6. Click Save.
7. Repeat this process for each URL that your iMIS administrator has given you.
8. Close the Local Preferences window.

Specifying the instance of iMIS to which you connect

Do the following to specify the instance of iMIS to which you connect:

1. Open Advanced Accounting Console but do not log on.
2. Click Cancel.
3. From the Advanced Accounting Console menu bar, choose Logon > Set Host Location.
4. On the Local Preferences window, click Edit.
5. When the Application Servers list becomes active, choose the URL to which you want to connect.
6. Click OK.
7. Close the Local Preferences window.
8. From the Advanced Accounting Console menu bar, go to Logon > Logon to Host. The logon area appears, with the Server field indicating the instance of iMIS to which you will be connecting when you log on.