NovaView 5.0 / 5.5 in Windows 2003 Server Installation Walkthrough
Before the deployment of Panorama NovaView Intelligence Server, you must first make sure the Windows server 2003 is ready for the installation. Please make sure your operating system is supported and all pre-requisites installed as described in this document.
Configuring Internet Explorer
The first thing you should do is to remove the option for “Internet Explorer Enhanced Security Configuration” this is suggested, and there are no side effects by removing it.
The only possible problem will be by user error, when accessing malicious websites.
This is not a firewall, and it does not in any way prevent hackers from gaining access to your server by other conventional means. It only prevents the current user from going out to the internet.
(Start >> Control Panel >> Add or Remove Programs >> Add/Remove Windows Components)
However if you feel insecure about removing this option, you’ll have to deal with all the security pop ups, and it does in many ways hinder the way how NovaView Web Access, NovaView Desktop, and NovaView Administrator works.
To easy the pain of having to deal with the constant security pop ups, you can add in to the trusted sites the Machine name and/or the DNS name of the web site where the NovaView service will be hosted from, example: http://novaview.domain.com
(Internet Options >> Security >> Trusted Sites >> Sites...)
NOTE: By default the Require server verification... is checked and it needs to be cleared unless of using the secured server.
In the same tab go to "Custom level" and define "Automatic logon with current username and password".
Once you have completed the above, you must now configure IIS 6 in Windows 2003.
IIS Configuration – Part 1
Run IIS Manager, go to the Web Service Extensions , and set the ASP and ISAPI to be Allowed, as you see in the picture.
The next few steps will apply after NovaView server installation.
Windows Application Event Viewer
It is also suggested to set the Application Event Viewer of Windows to recyle the log to prevent out of space problems.
To do so, go into the Application Event Viewer properties, and select the option “Overwrite events as needed”
Installing Microsoft Java Virtual Machine
A pre-requisite before installing the NovaView server is to have Microsoft Java VM installed, else many web enabled functions will not work, and it will not let you continue the installation.
To verify if you require to install MS JVM, go to the Advanced tab (Internet Options >> Advanced) scroll down, you should be are able to find Microsoft VM is listed in it.
If it is not listed, then you should run the file msjavx86.exe
It will ask you to reboot the computer after it finishes, you must do so in order for it to work properly.
If you already had Microsoft VM installed, it might be corrupted or incomplete, if that is the case. Run the file unmsjvm.exe
It will remove the current instance of Microsoft VM; you might be required to restart the computer.
Once it has been successfully removed, you can then install again file msjavx86.exe
Note: You can download a copy of these two files mentioned here in our Download section of this web site.
When you have successfully completed MS JVM install, proceed with the NovaView server installation.
Analysis Services (OLAP) 2000 Requirements
Another pre-requisite before installing NovaView Intelligence Server is to have Microsoft OLAP installed in the same machine hosting Panorama NovaView, this is required to ensure full compatibility, and have access to all the files provided by the installation of Analysis Services 2000.
If by some unknown reason you can not have OLAP 2000 installed in the same machine as Panorama NovaView, then at the very least you must have OLAP 2000 Management and Client Tools installed:
- Analysis Manager
- Decision Support Objects
- Client components
Analysis Services (OLAP) 2005 Requirements
Software Requirement to run NovaView 5.0 with SQL OLAP 2005 in a separate machine
- Microsoft Java Virtual Machine
- ADOMD.NET
http://www.microsoft.com/downloads/details.aspx?FamilyID=790D631B-BFF9-4F4A-B648-E9209E6AC8AD&displaylang=en
Download the installation file ADOMD.NET.msi and the hot fix file ADOMD.Net-KB893091-v8.00.0991-x86.EXE- Microsoft SQL Native Client (included in your SQL OLAP 2005 CD)
- Microsoft SQL Server 2005 Support Files (included in your SQL OLAP 2005 CD)
5. Microsoft SQL Client Components (see picture for details)
Note: Please refer to this KB article NovaView Server 5.0 (x86 32bit) Software Requirement for more details.
NovaView Intelligence Server Installation
Before you start the NovaView Server installation, it is strongly suggested to review these 2 KB articles:
NovaView Server 5.0 (x86 32bit) Software Requirement
Troubleshooting J# (JSharp) configuration problems
To install the NovaView server, run the file NovaView Intelligence Server.exe from the files unzipped you have obtained from Panorama Software.
Note: The installation process uses the InstallShield wizard, which means if you get any error during this process, it usually means you have problem with the InstallShield files, or your account does not have enough permission to proceed with the installation. There are several known issues with the InstallShield.
Feel free to access our Panorama Support Knowledge Base and/or the InstallShield Knowledge Base (http://support.installshield.com) for details for the errors you get.
Once the InstallShield wizard completes the unpacking, and prepared the install, you should see this Welcome screen from Panorama Software.
You must read and accept the License Agreement, before you can continue the install, if you do not feel you can comply with the agreement, please cease the installation and feel free to contact Panorama Software operation manager to reach an agreement.
If you do decide to continue, please locate the License Key (License.XML) you received by email from the Panorama Support Team, and copy it to the C:\
C:\ is the default location, where the installation package will look for the License key. It is not really necessary to keep it in C:\ but you will have to point the installer to the correct location, where the License.XML file is located, if you do decide to keep it somewhere else.
Confirm that it is the . If you are not sure, please contact Panorama Support Team.
Confirm the location where you want the NovaView server to be hosted from. This directory will later on be shared in IIS to become the NovaView Web Access.
Even if you choose the files to be installed to another drive letter such as D: drive, there will still be many files that will be stored in C: drive, these are the system files, and can not be allocated to another location.
Once the files are copied and installed properly, you’ll be prompted to create the Panorama database in the SQL server.
You may choose to do it now by selecting YES, or you might want to do it manually later on, by selecting NO
If you selected YES, then you’ll be prompted to type in the Name of your SQL server. If your SQL server is in another machine, it’s strongly recommended to use its NetBIOS machine name or its DNS (FQDN) name if available.
You may leave it in LocalHost if both the NovaView server and SQL server are in the same machine, but if you experience problems after the installation, you might need to re-install using the DNS name or NetBIOS name to correct the problem.
You may also change the Database name to be used, the default is “Panorama” you may call it anything you like.
The database will be used to store various settings, for the cache, logs, and other advanced features of NovaView Web Access, and NovaView Administrator.
Note: If you encounter any error message related to SQL server not being found, or your Credentials are not valid. You might want to abort and continue the installation without creating the database, then after the installation is completed you can created the database manually.
InstallShield will use your current windows account to access the SQL server you typed in, if your account does not have right to access, created, administer SQL servers, then it is most likely you will get an error message, and not able to complete this step.
Once everything has been properly installed, you’ll get this confirmation screen.
IIS Configuration – Part 2
After the completion of the NovaView server install, it’s time to verify a few settings in IIS Manager.
Run IIS Manager, open Default Web Site, if you installed NovaView to a different web site then open the corresponding web site.
Edit the properties of the Panorama virtual directory in IIS, select the Virtual Diretory tab, then select the Create button.
Then select the Configuration button
Select the Options tab, and make sure “Enable parent paths” option is selected.
Next step is to verify the security access settings for the Panorama virtual directory, in the Directory Security settings.
Make sure it’s configure to only use “Integrated Windows Authentication”
The other modes are possible, but not desirable, end users might be forced to login manually, or they might become Anonymous if they don’t get authenticated properly.
IIS Settings for JSharp
For the J# Client to work properly, the JSharp folder in the IIS must be set to Script Only, see picture for detail.
Note: There are a total of 3 folder that requires this setting for Panorama NovaView Server to work with J#:
- Deliveries/Config/JSharp
- JSharp
- Temp/JSharp
If you are having difficulty with J# please see KB article Troubleshooting J# (JSharp) configuration problems for details on how to solve commonly known issues with J#
Optional IIS Setting
To simply the access for end users, you might want to add the Welcome.htm into the Documents tab of the Panorama virtual directory properties.
Troubleshooting Starting Service Problem After Installation
It might take a long time for the NovaView server to start up properly the first time.
This usually will happen if you had trouble during the installation process of connecting to the SQL server.
Wait for the NovaView server to start, and then run NovaView Administrator, and verify the UDL settings for the SQL data connection string.
(Panorama Administrator >> Properties >> Database >> Edit)
Make sure you have the correct SQL server name, and the correct Database name. Open SQL Manager and make sure the Database is indeed listed, and accessible. Verify the permission level of the database intentede for NovaView server use, to be accessible by the users to have read / write access.
Note: If you created a new database manually in the SQL server, make sure to remember to Create the tables, by selecting the Options button, then selecting the option to “Create Tables” as shown in the picture above.
Then test the connection, to make sure the connection is working properly.
Note: When using the option “Windows NT Integrated security” it will login with the current web user authentication to the SQL server. Which means you will have to grant access for read / write to the SQL database for all related users.
If you do not want that, we suggest using the second option of “Specific user name and password” in which you can set an account to be used to connect to the SQL server.
Make sure the password is Saved by selecting the "Allow saving password" option.
If you created a new database manually in the SQL server, make sure to remember to Create the tables, by selecting the Options button
You should get “Test connection succeeded” if everything has been configured properly.
Once you have completed the modifications you should restart the NovaView Server service. Now the service should start up right away.
| < Prev | Next > |
|---|