The following procedure assumes a basic knowledge of the Windows operating system, Jim2 Client and the Jim2 Server Console.
Please be sure to take note of the Install Checklist first.
▪After SQL install, ensure SQL Protocols are enabled for the new instance via Configuration Manager (full SQL install only). ▪Update SQL Authentication to mixed, and update password policy (full SQL install only). ▪Enable sa user and update password (full SQL install only). ▪Install Jim2 and upgrade to latest version. Windows Powershell version 5.1 is a requirement if powershell scripting is to be used. If Powershell 5.1 is not already installed, you will need to install Windows Management Framework 4.1 from here: https://www.microsoft.com/en-us/download/details.aspx?id=54616 for more information. ▪Update/create firewall rules on the new server (see below). ▪Turn off email functions in Jim2, and ensure no more emails are going in and out.  ▪Backup and restore primary databases. ▪Disable Jim2 and Jes service on existing server. ▪Create Jim2 Share for folder location %\Program Files(x86)\Happen\Jim2 (read for everyone on the Jim2 folder). ▪Update Jim.ini in the Jim2 folder, and set to the database by default. ▪Configure Jes from backup XML, as per previous section. That is, assuming Jim2 is installed on C:\, and the Jes file to back up and restore on the new server is located here: C:\Program Files|Happen Business|Jes\bin\Jes_Config_Jim_XXXX. Stop Jes on the new server, replace the file, then start Jes. ▪Jim2 Mobile transfer request to Happen (if applicable). ▪New licence key installed. ▪Test with Jim2 Client on workstation and server. ▪Ensure backup configured on new server. ▪Enable email in Jim2 on new server. |
Summary
Install Jim2 on the new server from the latest installer: https://installer.happen.biz/Installs/Jim2Setup/4.5/Jim2Setup.exe.
|
The version of SQL must be the same or newer than that on the old server, ie. if SQL 2022 was installed on the old server, install SQL 2022 or a later version. |
▪The latest installer will download SQL Express by default, if selected to do so.
▪Download SQL Express 2016 from SQL Server 2022 | Microsoft.
|
If SQL is installed manually (not via the Jim2 Installer), ensure TCPIP is enabled via the SQL Server Configuration Manager:
If SQL Express 2016 is installed manually, it is recommended to name the instance JIM2. |
▪Download and install MS Management Studio (optional, but advised):
–From https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms.
–Click Download. Scroll to the lower portion of the file selection options.
–Download and install MgmtStudio 64BIT\SQLManagementStudio_x64_ENU.exe
Before logging on to the database, download and install the Latest Jim2 Update from www.jim2.com.au/support/latest-update/.
|
If installing an earlier version of Jim2, upgrade that database first. |
▪Confirm Jim2 works, and that log on to the Demo database.
Register the new server with Happen, and install the licence key:
▪To register, log on to the Demo database with the username: sys and password: sys.
▪Click Register, fill in the form and send to Happen.
▪The key from Happen will have instructions on how to install.
|
The key from the old server cannot be used on the new server. A new key must be supplied, as the key relates to the machine Jim2 is installed on. |
Do a Jim2 Backup of the database from the Jim2 Server Console of the Old Jim2 Server (ensure to stop email delivery as per the checklist above).
Restore the Backup on the new Jim2 Server.
Once the backup is restored, run the Jim2DBUpdate application
Once logged on to the Jim2 database, move the Jes configuration to the new server as well:
▪Copy the XML file for the Jes instance from the old server, usually found here: C:\Program Files\Happen Business\Jes\bin\jes_config_jim_yourcompanyname.xml
▪Paste it into the same directory on the new server.
▪Create a new Jes service using the Jim2 Configuration Manager (Jim2CM.exe).
▪The name should match the Jim2 database, and be the same in the Jes configuration file name: e.g. Jim_yourcompanyname.
▪When creating the Jes Instance, Jim2CM will ask to re-use the settings. If found, click Yes.
▪When starting, there may be some errors because the same directories are not set up on the new server. Either fix them in the Jes configurator, or create them on the new server as required.
|
Jim2 Mobile If the Happen Cloud (Jim2 Mobile) has been used on the old server, the configuration will move to the new server. Advise Happen Business (email support@happen.biz) when the new server is live so the cloud access can be changed from the old to the new server. Until that time there will be Cloud Server access errors (multiple Jim2 Servers are not allowed to connect at the same time).
Jim2 eBusiness Website (JEF) If the company has a Jim2 eBusiness website, contact us (support@happen.biz) for further information. |
▪It is best to get the new server up and running with plenty of spare time before decommissioning the old server. ▪The new server can be registered at any time. ▪The Jes service cannot be started until the Jim2 database is restored. ▪The Jes service name needs to match the Jim2 database name. ▪If any of these steps are unclear, please email support@happen.biz for assistance. |
Allow access for the following applications (do not open ports only). Configure the applicable rules as per below. One rule is required for each of these applications: ▪SQL Server: Sqlservr.exe (usually found in: C:\Program Files\Microsoft SQL Server\MSSQL<version>.<instance_name>\MSSQL\Bin\ ) ▪SQL Browser: sqlbrowser.exe (usually found in: C:\Program Files(x86)\Microsoft SQL Server\<version>\Shared\ ) ▪Jim2 Server Service: jim2server.exe (Usually found in: C:\Program Files\Happen Business\Jim2Server\ ) ▪Jim2 eBusiness Server: jes.exe (Usually found in: C:\Program Files\Happen Business\Jes\Bin\ )
The rules only differ when it comes to the Name on the General tab, and Application selected on the Programs and Services tab.
|
It is recommended that the primary Jim2 executables are excluded from real time scanning, both at the desktop and server level. Where possible, the Happen Business Program file folders should be completely excluded. |
C:\Program Files\Happen Business\ C:\Program Files(X86)\Happen Business\ |
C:\Users\frank.lampard\AppData\Local\Happen Business\LocalJim2\ |
C:\Program Files (x86)\Common Files\Happen Business\JimClient\ |
Jim2Server.exe Jes.exe JimReportServer.exe Jim2.exe Jim2Client.exe |
Jim2.exe Jim2Client.exe |
Jim2.exe Jim2Client.exe |
|
Server exclusions for SQL Files as per Microsoft recommendations: https://support.microsoft.com/en-us/kb/309422 should be used. |
After Jim2 has been installed on the new server, the following steps are required to provide users access to the Jim2 Client.
|
Jim2 does not need to be installed on Client computers. |
Share the Jim2 folder on the server, providing Everyone Read Access.
C:\Program Files (x86)\Happen Business\Jim2
Once the folder has been shared from the Client side, create a shortcut to the Jim2.exe contained within the Jim2 folder, and place it on the user's desktop.
Further information
Change the Name of Your Database
Jim2 Server Console Authentication
Move Jim2 Database to a New Location