Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

 

Prerequisites

Microsoft Windows 7 or later

Jiwa 7 supports the following operating systems:

  • Windows 7
  • Windows 8.1
  • Windows Server 2008R2
  • Windows Server 2012
  • Windows Server 2012R2

Microsoft SQL Server 2008R2 Express or later

For evaluation purposes, you do not need to install an SQL Server. The installation will install MSSQL Localdb and create a connection to a demo database automatically. The limitation with localdb is that it is single user only - for multiple concurrent users, Jiwa 7 requires a connection to an SQL Server. You can install the SQL Server on the same machine as Jiwa 7, or any machine accessible via the network. Jiwa 7 also supports Microsoft Azure SQL servers. Jiwa 7 supports the following SQL Server versions:

  • SQL Server LocalDB
  • SQL Server 2008R2
  • SQL Server 2012
  • SQL Server 2012R2
  • SQL Server 2014
  • Azure SQL

NOTE: Jiwa uses SQL Server authentication, so when installing Microsoft SQL Server, chose mixed mode authentication when prompted during the installation process. This can also be changed post-installation.

 

Jiwa 7 Installation Package

The installation package can be downloaded from the Jiwa support portal.

 

Install Jiwa

Locate the setup.exe file from the directory where you stored it during the download. Right click on it and select “Run as administrator”. The installation dialog will open.

Read and Accept the License Terms and Conditions and select Install.

Jiwa will now run through the installation process. This may take several minutes.

At the conclusion of the installation you may be prompted to reboot to complete the installation. The Crystal Reports component Jiwa 7 uses for the reporting engine requires a reboot after installation - Jiwa 7 can still be used without this reboot step provided no reports are generated.

 

Create a Demonstration database

Double-click the Jiwa 7 shortcut on the desktop.


The login dialog will appear.

 

There will already be a connection and demo database created for you using the installed LocalDB database - if you do not need to evaluate Jiwa with multiple concurrent users then you need proceed no further - just enter the password "password" (without quotes) and then click the "connect" button and you will login to the locally installed database. You can then disregard the remainder of this guide.  If you do wish to connect to an SQL server, then click on the "databases" button and then click Next to begin the wizard.


Select the "Create a new Jiwa demonstration database" option.


From the Server Dropdown select the MS SQL server where Jiwa 7 is installed, type in “sa” SQL Login enter “sa” and the relevant password you created in Step 1 and select Next.

 

Type in the name that you would like the database to use in MS SQL. Only use alpha-numeric characters and to not leave any blank spaces in the name. The Checkbox ‘Please automatically add the database to my connection list’ is ticked by default. This will create a Connection with the same name as the Database Name. The connection name can be changed to something else.   Selecting the Reset all staff SQL logins and passwords checkbox allows the administrator to reset the SQL Passwords for the ‘JiwaUser’ and the ‘JiwaReports’ users. NOTE: This is optional. By default the passwords are set to the Jiwa Standard password


Jiwa will then give a summary of the database that it will create and select Finish.


Jiwa will now build the database and it may take a few minutes – be patient :)


When it is finished, select Close and you will be returned to the Connect to Jiwa screen with the Connection Name already selected for you.

 

Creating a Connection to a Database

If you unticked the “Please automatically add the database to my connection list’, when you created a database then you still can create a connection manually.


From the Login dialog select Connections.

 

On the Connection Wizard Welcome dialog select Next


Select Create a new Connection and select Next


Enter a Connection Name (this one can have spaces)

 

Select your MS SQL Server from the drop down or enter the server name manually.  SQL Login and SQL Password are automatically populated with the jiwalogin user and the password jiwaapplicationlogin.  Then use the drop down menu to select the database from those available on the SQL server and select Next


Jiwa will then give a summary of the connection that it will create. Check the details and if they are correct select Finish then Close.

 

Now that the connection has been added, Jiwa will return you to the Jiwa Login Dialog.

 

Log in to Jiwa

The login to a Jiwa Demonstration database is admin and the password is password

 

Select Connect.  You are now ready to use Jiwa.

 

Creating a Connection Template

When Jiwa is installed in a multi-user environment (such as Microsoft Remote Desktop Services), it can save much configuration time if all system users (and any users added in the future) are given a default set of connections from a common template.

When Jiwa is run it first looks for %appdata%\Jiwa Financials\JiwaConnections.xml. This is where the list of connections for the current user is stored. If Jiwa does not find this file, it then looks for a file called "JiwaConnectionsTemplate.xml" in it's installation folder. If this file is found, it is copied into %appdata%\Jiwa Financials\ as "JiwaConnections.xml". If it is not found, then a blank "JiwaConnections.xml" is created in %appdata%\Jiwa Financials\.

Those steps again:

  • Look for a list of connections in %appdata%\Jiwa Financials\JiwaConnections.xml
  • If no such file is found look for <Jiwa Installation Folder>\JiwaConnectionsTemplate.xml
  • If JiwaConnectionsTemplate.xml exists, copy it to %appdata%\Jiwa Financials\JiwaConnections.xml
  • If NO JiwaConnectionsTemplate.xml exists, create a blank %appdata%\Jiwa Financials\JiwaConnections.xml

So after installing Jiwa in a multi-user environment, a template of connections can be constructed. Run Jiwa and create/delete connections as required. Exit Jiwa. Copy the file at %appdata%\Jiwa Financials\JiwaConnections.xml to <Jiwa Installation Folder>\JiwaConnectionsTemplate.xml.

Now, any user that runs Jiwa that does not already have their own set of connections will be given a copy of the template of connections as a base for their own connection list.

 

Using Jiwa

The Jiwa menu is displayed in the left hand navigation pane. It can be collapsed by clicking the ‘Minimize Navigation panel’ button from the navigation pane header. This provides more screen visibility for the actual form you are in. The details to using Jiwa can be found by clicking on the Help button on each open form.

 

Troubleshooting

Password Policy

Sometimes, Jiwa demo might have problem installing due to the password policy in MS SQL. To correct this, you need to use MS SQL Management Studio.  Run MS SQL Management Studio, connect to the SQL Server, and then expand Security > Logins.  Of interest are the JiwaLogin, JiwaReports and JiwaUser logins.


Right click on JiwaLogin and select Properties.

 


On the Login Properties screen, remove the tick from the Enforce Password Policy tick box and OK.

 

Repeat for JiwaUser and JiwaReports.

Changing Authentication Mode

You can change the Authentication mode through SQL Server Management Studio, the MS SQL Server Database Engine is set to either ’Windows Authentication mode’ or ‘SQL Server and Windows Authentication mode’. After installation, you can change the authentication mode at any time.

 

If ‘Windows Authentication mode’ is selected during installation, the ‘sa’ login is disabled and a password is assigned by setup. If you later change authentication mode to ‘SQL Server and Windows Authentication mode’, the ‘sa’ login remains disabled. To use the ‘sa’ login, use the ALTER LOGIN statement to enable the ‘sa’ login and assign a new password. The ‘sa’ login can only connect to the server by using SQL Server Authentication.

Change security authentication mode

In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.  On the Security page, under Server authentication, select the new server authentication mode, and then click OK.


In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.

 

In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.

Enable the sa login

In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.  On the General page, you might have to create and confirm a password for the login.


On the Status page, in the Login section, click Enabled, and then click OK.

 

Cannot Connect to the SQL Server

If you are having trouble connecting to the SQL Server, you should begin the troubleshooting process by using SQL Server Management Studio - this is the official tool used to connect to and manage Microsoft SQL Servers. Microsoft off this as a free download available from [here]. After installing, confirm that you still cannot connect to the SQL Server by attempting a connection using the SQL Server Management Studio:

 

 

Look carefully at the error message given. If you have simply got the username or password wrong, the error message will reflect this.

 

If you are indeed having connectivity issues rather than an incorrect username or password, the error message given may be something more like:

 

There will normally be a delay between clicking the connect button and receiving the error message if it is connectivity issue rather than an authentication issue. This is because in the case of an authentication issue, the connection is made immediately but the server refuses login, whilst in the case of a connectivity issue the SQL Management Studio will try over and over to connect for around 15-30 seconds before giving up and reporting the error.

 

There are 3 troubleshooting steps we can take in the case of a connectivity error.

Open Firewall Port

The server machine may have a firewall enabled that is blocking incoming connections to the SQL Server. All editions of SQL Server except for SQL Server Express will automatically create an "Allow" rule in the firewall during installation if installation is taking place on a Windows Server operating system. If installation is occurring on a workstation operating system (i.e. Windows 10, Windows 7) then the "Allow" rule is *not* automatically created. SQL Server Express edition will never create an "Allow" rule. The default port that Microsoft SQL Server accepts incoming connections on is TCP Port 1433. You should ensure that any firewall on the server is allowing connections on this port. Below are the steps to allow connections on this port for Windows Firewall on Windows Server 2012 R2.

 

1. Right click on the Windows Start menu and choose "Control Panel".

2. From the Control Panel choose "Windows Firewall".

3. From the Windows Firewall choose "Advanced settings:

 

4. Create a new "Inbound Rule" by right clicking on the "Inbound Rules" node on the left and choosing "New Rule..." from the context menu that appears.

 

5. Select "Port" as the rule type and click Next.

 

6. Select "TCP" and a "Specific local port" of 1433. Click Next.

 

7. Choose "Allow the connection" as the action. Click Next.

 

8. Ensure that Domain, Private, and Public are all ticked for the profile. Click Next.

 

9. Give the new rule a name of "SQL Server". Click Next.

 

10. Click Finish.

 

SQL Server Management Studio should now be again used to attempt to establish a connection. If the connection still fails, follow the second troubleshooting step provided below.

Set SQL Server Port

If opening port 1433 on the firewall as per above does not solve the connectivity issue, then we must check that the SQL Server itself is listening on the desired port (TCP port 1433). To do this the "SQL Server Configuration Manager" is used.

 

1. Launch the "SQL Server Configuration Manager". In Windows Server 2012 R2 this is done by clicking on the Start menu, typeing "SQL Server Con", and then clicking the "SQL Server 2014 Configuration Manager" icon which appears on the right.

2. Expand the "SQL Server Network Configuration" node on the left.

 

3. Click "Protocols for SQLEXPRESS" (this may vary depending on the version of SQL Server installed).

4. Right-click on "Named Pipes" on the right and choose Disable (if it isn't already disabled).

5. Right-click on "TCP/IP" on the right and choose Enable (if it isn't already enabled).

6. Double-click on "TCP/IP" on the right.

 

7. Click on the "IP Addresses" tab, and scroll to the bottom to the "IPAll" section. Clear the value for "TCP Dynamic Ports" and enter the value "1433" (no quotes) for "TCP Port". Click OK to close the TCP/IP Properties window.

 

8. For the changes to take affect, the SQL Server must be restarted. To do this, click on the "SQL Server Services" node on the left.

 

9. In the right-hand pane, right-click on "SQL Server" and choose "Restart".

 

After a minute the SQL Server Service will have restarted and will be listening on port 1433. SQL Server Management Studio should now be again used to attempt to establish a connection. If the connection still fails, follow the third troubleshooting step provided below.

Allow Remote Connections

If you are able to connect to the SQL Server (i.e. using SQL Server Management Studio on the server machine itself), then you should ensure that the SQL Server is configured to accept connections from remote computers.

 

1. Connect to the SQL Server using SQL Server Management Studio (i.e. on the physical server itself).

2. Right click on the server node and choose "Properties".

 

3. On the Server Properties windows, choose "Connections" in the left hand pane.

 

4. On the right hand pane, ensure that the "Allow remote connections to this server" is ticked (see screenshot above). If it is not, tick it, and restart the SQL Server Service for changes to take affect.

 

  • No labels