Maintenance

Backing up your iMIS database ensures that your data is secure. Having a solid monthly routine in place minimizes the amount of data you could lose in a disaster.

🚧 Warning

Avoid using third-party backup SQL agents, which might cause problems when restoring your database.

Be sure to set up a scheduled maintenance plan in SQL Server to reorganize and rebuild your iMIS database indexes on a routine basis, so that you have the best possible system performance. The larger the iMIS database, the more important this becomes in keeping performance up.

See MSDN to find out more about creating a maintenance plan. While every database is different and will have different requirements, a common routine is to reorganize your indexes daily and to rebuild them weekly.

If the name of the server that hosts the iMIS server ever changes, you must uninstall and reinstall iMIS to enable remote installations and future upgrades of iMIS.

The SMTP server that you specify during installation is written to the web.config files for each iMIS application installed during that session. If you need to change SMTP server settings after iMIS has been installed, you must manually edit the respective web.config files to specify the new SMTP server.

Do the following to change SMTP server settings:

1. Modify the web.config files for all instances of your iMIS to specify the domain name of the SMTP server to use for each:
   • On each iMIS server host, open the web.config files for each iMIS application:
     • iMIS default location:
       • C:\Program Files (x86)\ASI\iMIS\Net\web.config
       • C:\AsiPlatform\Asi.Scheduler_[your instance]\web.config
   • In each web.config file, search for the <network> element declaration and modify the value of the host attribute to specify the domain name of your organization’s SMTP server. For example:

   <network host="mysmtpsrv.myorg.org"…

   📘 Note

   In the <network> element declaration, you can also specify port and authentication information for your SMTP server to ensure that iMIS can find and log on to the SMTP server in your environment. For details, refer to your Microsoft ASP.NET documentation.

2. Restart each iMIS server on which you modified the web.config file.

You must temporarily stop Internet Information Services (IIS) before attempting to restore the iMIS database. Otherwise, the service can lock the database and prevent the restoration.

Run the following command from a command prompt to ensure that IIS is stopped:
iisreset –stop

Once you have restored your database, you can run the command iisreset –start to restart IIS.

📘 Note

The SQL Service Broker must be enabled after a database restore. See Enable the SQL Service Broker for more information, please.

If the initial start time is too slow even after rebooting or restarting IIS, you can edit settings to lower the startup time.

1. Stop the AsiScheduler application.
2. Edit the web.config files.
3. Find the <SystemParams> section and add the following:

                        <!-- Url to the application server this is installed for. -->
<add key="ImisWebServerUrl" value="http://localhost/iMIS/"/>
<!-- Value given in minutes. Default value is 15. -->

<add key="PingInterval" value="15"/>
<!-- Comma-separated list. Example value: 
	"http://server1/iMIS/,http:server2/imispublic/,..." -->
<add key="AdditionalUrls" value=""/>

4. Recycle the AsiSchedulerPool app pool, then enable the AsiScheduler application for it to take affect immediately.

📘 Note

There is also a keep-alive service for all RiSE-managed sites, to automatically pre-load sites in IIS if they are restarted, to improve the load time for the first browser request. You control this service through the Asi.Scheduler web.config file.

When the product setup.exe creates a new iMIS database, two SQL logins are created on the SQL Server instance that are used for system-level authentication of database transactions initiated by an iMIS user. These special logins prevent the need for any iMIS user to have a defined login or user on the SQL Server instance or iMIS database. Neither login is a member of any server role.

• manager_<db> (where <db> is your iMIS database) is used by every iMIS user record that is a member of the SysAdmin role in Advanced Accounting Console.
  • This login is a member of the database roles db_owner and public.
  • As a member of the db_owner role, it enables activities such as rebuilding tables from Advanced Accounting Console.
• imisuser_<db> (where <db> is your iMIS database) is used by every iMIS user record that is not a member of the Advanced Accounting Console SysAdmin role in Advanced Accounting Console.
  • This login is a member of the database roles IMIS and public.
  • Not a member of the db_owner role, activities such as rebuilding tables are unavailable.