Insert excerpt Getting Started with IMOS Documentation Getting Started with IMOS Documentation nopanel true
This is a Key Topic, with high value for all users.
...
Step | Action | Comment | ||||||
1. | Make an IMOS home directory, for example D:\veson\. | Install IMOS in a location that users can access: either on a file server, if users will be running IMOS from their desktops, or in a place accessible to a Citrix or MS Remote Desktop Services application server, if IMOS will be accessed that way. | ||||||
2. | Extract the installer from the downloaded Zip file to the desktop. | The IMOS installer is distributed in a Zip file format. You can download the file from the Client Center: http://clients.veson.com. For sign-in details, contact Veson Nautical Support. | ||||||
3. | Run imosv#.#.#-extractor.exe, where #.#.# is the IMOS version number. | Click Yes when prompted to extract IMOS. After initial decompression, the IMOS Extractor opens. Select the directory created in step 1 as the installation location, and click Extract Files for New Install. The installer requests an installation key, which can be found on the front page of the Client Center, above your account manager's contact details. Note: If you do not have an installation key, you can still extract IMOS without one. Click No when prompted to input a key, and it will begin the extraction. The extracted files are placed in the The installer also requests elevated privileges (and admin credentials) via Windows User Access Control if you are not set up as an admin. | ||||||
| Modify the Configuration files provided with the installer: | Move the If no application server is used, the config files must be edited on each client computer. | ||||||
imos\services\imosmsg.exe.config (XML Configuration File) |
The default value provided with the file is <add key="prod" value="prod" /> For each key in this file; there must be a corresponding line in imos\exe\imosshell.exe.config and imos\services\config\imosEnv.xml Notes:
| |||||||
imos\exe\imosshell.exe.config | On the server, you can configure the IMOS shell to display one or more environment options. When you open d:\veson\imos\exe\imosshell.exe.config (XML Configuration File) in Notepad++, it has the following sections:
| |||||||
5. | Restore the base V7 database provided with the installer or a V7 database backed up from an existing installation. | First-time installs are typically provided with a base database (with a name like imosv#.#.#-blank-schema#.bak, where #.#.# is the version number) in the imos\db directory that is then populated with initial master data. https://www.dropbox.com/s/rp6qjtyanw6pljj/imos711_onboardtraining_112021.bak?dl=0 or https://www.dropbox.com/s/kgwu09xlr4nx4eq/Demo20200605.7z?dl=0 are better example to restore as it contains more data.Inside Microsoft SQL Server Management Studio, right-click the Databases folder under your database instance and click Restore Database. For Source, select Device and add the .bak file that you received with your first-time install, as per the above location. It will be in the DB folder from the extracted IMOS file. Right-click the server instance and then click Properties. On the Security tab, change the Server Authentication to SQL Server and Windows Authentication mode. Then, restart the SQL instance so that the new settings can take effect. (Within SQL Server Studio, Right click on the SQL instance and click Restart) Note: If the Security tab does not appear in your database, just ensure that the server settings are set up correctly. | ||||||
6. | Create a new SQL Server sign-in for IMOS and give it db_datareader, db_datawriter, and db_owner permissions on the IMOS database. | See the screenshots below. Note the password permissions level. Expand the Security file, right-click Logins, and then click New Login. | ||||||
| Modify the Configuration file provided with the installer: | This file is used by the Messaging Service running on the application server and maintains database sign-in information for each of the configured IMOS environments. It has the following sections:
| ||||||
8. | Place the license file provided on the Client Center in imos\services\config. | Each client receives an individual license file that unlocks features in IMOS to match those purchased, for the appropriate number of users. | ||||||
9. | To register the service, open Command Prompt with administrator privileges (right-click Command Prompt and select Run as administrator), then, from the imos\services directory, run: | The service will be registered and run on the application server. If you are running multiple instances of the IMOS7 services concurrently (advanced):
| ||||||
10. | Start the IMOS Messaging Service. | Start the service from the Services Control Panel in Windows (Control Panel -> System and Security -> Administrative Tools -> Services). Double-click the IMOS Messaging Service and set it to start automatically by setting the Startup type to Automatic. | ||||||
Connecting to Veslink via VXP Method | ||||||||
11. | Do this only if you are using Veslink in production: Connect your Veslink site to your IMOS environment. |
| ||||||
12. | Do this only if you are using a Test Veslink site: Connect your Test Veslink site to your Test IMOS environment. |
| ||||||
Connecting to Veslink via Websocket MethodNote: Websockets are supported on Microsoft Server 2012 and later. | ||||||||
11. | Do this only if you are using Veslink in production: Connect your Veslink site to your IMOS environment. |
| ||||||
12. | Do this only if you are using a Test Veslink site: Connect your Test Veslink site to your Test IMOS environment. |
|
...