Installation Dino Explorer Suite Guide Installation Guide. Version 6.2.0

Transcription

1 Dino Dino Explorer Explorer Suite Installation Dino Explorer Suite Guide Installation Guide Version 6.2.0

2 Contents 1 Introduction Installing the Dino Server Installing Dino Client SQL Scripts Creating the DinoDB Upgrading DinoDB version Creating DinoDB users Database connection Dino Setup - Configuring the Database Dino Explorer License Appendix Dino Architecture Optimizing the database environment DinoMessaging - Automation Dino Explorer Suite Installation Guide v

3 1 Introduction The Dino Explorer suite, which runs on Microsoft Windows platform, needs a Microsoft SQL Server database properly installed and configured to function correctly. This document describes how to do this. Software Requirements In server side, Dino Explorer requires: Windows Server 2008 SP2 (x86 or x64) or higher; Microsoft SQL Server 2008 (x86 or x64) or higher; Microsoft.NET Framework 4.5; and Dino Explorer software. In client side, the requirements are: Windows 7 (x86 or x64) or higher; Microsoft Excel 2007 (x86 or x64) or higher; Microsoft.NET Framework 4.5; Access to Dino Explorer database; and Dino Explorer software..net Framework 4.5 Hardware requirements Processor 1Ghz; Ram 1GB; Disk space 2GB We suppose you have already installed the Windows operating system and the Microsoft SQL Server. To simplify the documentation, we use some definitions name from this moment: Dino Server DinoDB Dino Portal Dino Clients Server where you install the application software Dino Explorer software Server where you install SQL Server database software used by Dino Explorer Server where you installed the IIS Server software interface All workstations where you install the application software Dino Explorer software with client option Note: Please see topic Dino Architecture in the appendix. Dino Explorer Suite Installation Guide v

4 2 Installing the Dino Server To install the Dino Explorer Suite on the server, requires administrator privilege on mostly machines. If you do not have this privilege, check with the support team at servers, the procedure to be adopted for the software installation. Copy program installer (Dino<suffix>server.msi ) that supplied in the Dino Explorer software CD-ROM, to a known directory like c:\temp. Execute command prompt with administrative permission, on the cmd type cd c:\temp and then type Dino<suffix>server.msi. Upon successful start, some screens will be appear showing the installation instructions. The most important are: Type the folder where you wish to install the software. And then Finish button to complete Dino Explorer software. Dino Explorer Suite Installation Guide v

5 After completing the installation, we can see using windows explorer program, the folders and files installed on the Dino Server (Figure below). The next step is creating the database DinoDB in SQL Server using SQL Script. Dino Explorer Suite Installation Guide v

6 3 Installing Dino Client To install the Dino Explorer Suite on the workstation, requires administrator privilege. If you do not have this privilege, check with the support team at workstations, the procedure to be adopted for the software installation. For workstations with windows 7, you must first install.net Framework 4.5, included in the installation kit. Software packages that are packaged as Microsoft Installer (.msi) files, does not have the option Run as administrator" when right-click, such as.exe files. in such case you can run the cmd program with administrator privilege and run the msi setup. Upon successful start, some screens will be appear showing the installation instructions. The most important are: Type the folder where you wish to install the software. And then Finish button to complete Dino Explorer software. Dino Explorer Suite Installation Guide v

7 4 SQL Scripts Many facilities also have their database teams that will help you using these SQL scripts. Along with Dino Explorer, we provide some database scripts that will help in the create database (first time), version upgrade, create users and cleaning of historical tables. 4.1 Creating the DinoDB First Copy script files Copy the Script folder and its contents from Dino Server to the SQL Server where the database DinoDB will be created. In our example (see figure below), we put the folder and files on a local disk (drive D) under the SQL folder in SQL server. Note: All scripts have the attribute read only active, be sure to disable it, if you want to change any of the scripts. Dino Explorer Suite Installation Guide v

8 Second Edit DinoDB_Create Now you edit the DinoDB_Create.sql script using notepad.exe or other similar program. Some parts of the script can be changed, if you need. database_name NAME SIZE database_name FILENAME database_name Database_name NAME FILENAME SIZE Refers to the database as whole Specifies the logical name you will use within SQL to refer to the physical database file on the hard disk Is the pathname and filename pertaining to the location of the data on the hard disk. It must be a local hard drive. The default is C:\SQLServer\dinoDB_dat.mdf Specifies, in MB, the initial database file size. Multifile Groups Another thing you should have in mind at this time, is the amount of information collected on the mainframe and the maintenance of this information in your database, if you plan to store a lot of data and long time is recommended to use the grouping of SQL tables in multiple files groups. Using files and filegroups improves database performance, because it lets a database be created across multiple disks, multiple disk controllers, or RAID (redundant array of independent disks) systems. For example, if your computer has four disks, you can create a database that is made up of three data files and one log file, with one file on each disk. As data is accessed, four read/write heads can access the data in parallel at the same time. This speeds up database operations. Additionally, files and filegroups enable data placement, because a table can be created in a specific filegroup. This improves performance, because all I/O for a specific table can be directed at a specific disk. For example, a heavily used table can be put on one file in one filegroup, located on one disk, and the other less heavily accessed tables in the database can be put on the other files in another filegroup, located on a second disk. Dino Explorer Suite Installation Guide v

9 To create multi-file groups, replace all "-->>" by "" on the DinoDB_Create.sql script file After completed all changes in script file and save them, the SQL script is ready to be executed to create the database. You can use any option in below table. Sql Management Studio Winsql Sqlcmd SQL Server Management Studio (SSMS) is a software application that is used for configuring, managing, and administering all components within Microsoft SQL Server. The tool includes both script editors and graphical tools which work with objects and features of the server WinSQL is a database client and management application that connects to any database through ODBC Utility lets you enter Transact-SQL statements, system procedures, and script files at the command prompt Note: (*) You should avoid using the disk c because is where you install the operating system and in some cases also the applications and is not recommended to use this unit to put your database here. If you run out of disk space in disk c your server will stop working. Dino Explorer Suite Installation Guide v

10 Third Create DinoDB database Create the database folder and execute the script as shown below. Use the following commands: Create SQL folder => Mkdir \SQLServer Run script to create database => Sqlcmd.exe -S Servername U sa P xxxx i DinoDB_Create.sql Files created after database created (without multi-file groups) Files created after database created (with multi-file groups) Dino Explorer Suite Installation Guide v

11 Once the database is created, the next step is creating a connection with DinoDB in SQL Server. Note: if the message below appears: You must open the SQL Server Configuration Manager, then click in SQL Native Client 10.0 Configuration (32bit) > Client Protocols and enable the TCP/IP and Named Pipes protocols. 4.2 Upgrading DinoDB version If you are already use our software, when migrating to a new version, it may be necessary to adjust some tables in the database. To facilitate this process, provide the related script below to facilitate this process. DbUpgrade table Script Name From To Description version version DBupgrade_600.sql 5.x.x The upgrade script creates DB2 Accounting tables and SYSLOG table 4.3 Creating DinoDB users Use DinoDB_security script for create two database user, that will be used when you connect to database using database authentication method. First user (dinoldr) will be used to most important functions into DinoDB (load information in xxxdata tables and Summarize Historical tables, undo load function, compress data, purge data, etc.). Another user (dinousr) will be used for normal operations (execute queries and report using graphical interface or Command line interface (Dino Cmd)) For more details, see manual Dino Explorer Suite Users Guide. Dino Explorer Suite Installation Guide v

12 5 Database connection SQL Server allows two authentication methods. More details can be obtained together with your database team. SQL Server supports two authentication modes: Windows authentication mode and Mixed mode (Windows authentication and SQL Server authentication) The Dino support both methods of connection to the database. It is up to the user together with the database and security team of your facility to define the best suitable design your needs. 5.1 Dino Setup - Configuring the Database Dino Setup is the logical configuration of the Dino Database. It will look the configuration files that resides on the configuration directory into the config table. Set the Database Connection The most important configuration is the DinoDB Connection because all the Dino Configuration is saved on the database. So, any Dino utility, the first thing is to connect to DinoDB database. On Dino Server run the Dino Setup program. To do it, click on start menu -> programs -> Dino Explorer -> Server utilities -> Dino setup The Dino Setup program sends one of two errors down the attempt to connect to database Dino Server and DinoDB in different servers Dino Server and DinoDB in same server Dino Setup program can t find the database because the Dino.Config doesn t exist yet. So, click the OK button at the message. Dino Explorer Suite Installation Guide v

13 The Dino database configuration panel will be appearing for you to enter the parameters. Type the database servername. Type database name. Test if the Connection it s ok When the parameters are ok and the connection has been established, the success message will be shown. Clicking on the Ok button you will see the main form of Dino Setup. Run the Dino Setup Now, just click on the Init button to load the database configuration. The success message Load database completed!!! will be displayed. Dino Explorer Suite Installation Guide v

14 Connection setup The Dino configuration file, called Dino.Config is created at the next locations for the following operating systems: Windows 7 (x86 and x64) or higher Windows Server 2008 SP2 (x86 and x64) or higher: C:\ProgramData\Dino Explorer> The Dino.Config file contains the string connection that be used by application to connect to database For all workstations where Dino Explorer was installed: you can create folder C:\ProgramData\Dino Explorer and copy the Dino.Config file to that folder or execute the process Set the Database Connection described above using any Dino Explorer application installed in workstation. At this time, we have: Dino Server installed; DinoDB created and configurated; Server utilities installed and connected to the DinoDB; Dino Explorer Suite Installation Guide v

15 6 Dino Explorer License Now, we re going to start the application for the first time. In order to work, Dino Explorer requires a license key, so the first time or when your license is expired you will experience the following message: Also, some options will be disabled. To load the product license, you must run the data loader program, do not worry about the message, simply click on the OK button. To load the license file, click on the Options menu ->Product license, to enter a product license registration form. On left screen, click on the Load button and locate a xml file license that was send by the Dino Explorer support team, after the license is loaded the license information appears in the right screen. The message informing License file loaded successfully is send. If all was executed correctly, the Dino Explorer Server is installed, configured and ready to be used. Dino Explorer Suite Installation Guide v

16 7 Appendix 7.1 Dino Architecture The Dino architecture is flexible and allowing create many different architectures, the user can modify it to increase reliability, scalability and resilience of the structure. In our example we use Mainframe Server One Server Two Client Workstation Two CECs (MVS1 and MVS2) running z/os Dino Server is an application server to communicate with all mainframe environments using Dino Messaging Service Dino Portal is an application server that performs several activities such as: Queries in DinoDB database and returns the result in the Web standard; Monitoring of process scheduling in the environment; DinoDB SQL server Workstation with Dino Explorer Client installed if you want our technical staff is available to assist you in studying the best topology that fits your environment. Figure 1 Dino Explorer Suite Installation Guide v

17 Figure 2 Note: The most important component of Dino Explorer Suite is the database DinoDB because all the queries and data are there. So consider a dedicated and powerful machine to the DinoDB. Dino Explorer Suite Installation Guide v

18 7.2 Optimizing the database environment Moving the tempdb place TempDb is a work database used by SQL to handle large volume of data to perform queries. If you need improve performance or manage storage space, you can move the original place of tempdb.mdf. To do that, follow the steps above: 1) Open SQL Server Management Studio. 2) Connect to the desired server. 3) Click the New Query. 4) Copy and paste the following into the query pane: USE master; GO ALTER DATABASE tempdb MODIFY FILE (NAME = tempdev, FILENAME = '{new location}\tempdb.mdf'); GO ALTER DATABASE tempdb MODIFY FILE (NAME = templog, FILENAME = '{new location}\templog.ldf'); GO 5) Change {New Location} in the pasted code (for both the tempdb.mdf and templog.ldf files) to the path of the new location. 6) Click Execute. 7) Go to the Control Panel and then Administrative Tools. Select Services. 8) Stop and Start SQL Server (MSSQLSERVER). 9) Go back to SQL Server Management Studio and open a new query pane. 10) Copy and paste the following to verify that tempdb has moved to the new location: SELECT name,physical_name FROM sys.master_files WHERE database_id = DB_ID('tempdb'); 11) Click Execute. 12) In the physical name column, you should see the path to the new location. Dino Explorer Suite Installation Guide v

19 7.3 DinoMessaging - Automation Keep in mind, that every time some Dino suite program runs, it uses the database configuration file (Dino.Config) to access the DinoDB server. In order to install and configure the Dino Server side of the automation, follow the next steps. The steps 1 to 3 can be executed for each LPAR. First - Create a LPAR entry in MVS Server List To connect to the mainframe the Dino Explorer utilities requires an MVS connection definition To do this run the DataLoader program on the Options menu, select MVS Servers. The connection refers the IP and port of mainframe task DXPLTCP. Please look at Dino Explorer Suite MVS Installation and Operations Guide for more details Server name Host name Set the name of your connection You can use the mainframe ip address or mainframe name registered in DNS. IP Port Define the port number that will be used to connect to the mainframe, default is After completing the parameters click the Save button and then click the Test connection to check if the parameters you configured are correct. After you create a mainframe connection, the connection string is saved on the configuration file: DinoConfig.xml Dino Explorer Suite Installation Guide v

20 Second - Install DinoMessaging Service To Install the service, you should run the ugly command on the command prompt (cmd) with Administrators rights. Note: On modern windows you should start the command prompt as Administrator, right clicking the cmd.exe: You should install one service for each LPAR you have. The DinoMessaging service can talk to only one LPAR Set folder => cd "C:\Program Files (x86)\dino 2015" Installing Service => C:\Windows\Microsoft.NET\Framework64\v \InstallUtil.exe /NAME=MVS1 /i DinoMessaging.exe The name of the service cataloged in the windows will be "Dino" + Name, in this example DinoMVS1. To facilitate the understanding of the structure, we suggest using the LPAR (SID) as the service name. Dino Explorer Suite Installation Guide v

21 You can see the service installed using services interface (services.msc in Administrative Tools). To add restart feature, on the Services interface, click properties and Recovery: Dino Explorer Suite Installation Guide v

22 Third - Adjust DinoMessaging parameters: During the service installation process, some entries were created in the registry. To change any value of these keys included in the registry, use the regedit program. These registry keys are located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\DinoMVS1\Parameters See the list of keys created in the figure below. Note: The key MvsServer is the name of the MVS connection you have created on topic above. Dino Explorer Suite Installation Guide v

23 LoadViews configuration LoadViews is a batch process to build the historical tables. you can run directly using the DataLoader utility or automated through the DinoUtil.exe command line utility. You can generate the a LoadViews configuration file in two ways: using DataLoader program, Data -> Import Data. Selecting option 4 (load views) and selecting on the product tabs, the views you want to have. At the end, you save the configuration on the database: file and save. The name you save is the same you supply on the DinoUtil -l LoadViewsName. Run the SQL script file AddLoadViews.sql to create a default LoadViews configuration on the DinoDB database. The script AddLoadViews.sql is inside the LoadViews.zip file in Script directory on Dino Server (C:\Program Files (x86)\dino Explorer 2015\Script) >> If necessary, contact your database team to execute the script to create loadviews << >> Be sure to change the name of the database in the script before running it << After SQL script execution you are able to see it on the DataLoader - Import Data menu. Select the File and Open the "LoadViews". You should see a screen such as below: You can review the default selections on the various views tabs. At the end, you save your configuration. The name you save is the same you supply on the DinoUtil -l LoadViewsName. For more details about Load View option, see manual Dino Explorer Suite Users Guide Dino Explorer Suite Installation Guide v

24 Automation Script file We provide two examples of batch files that are inside the zip file. See below the list of files that are inside the zip file. The zip file can be found in Script directory on Dino Server (C:\Program Files (x86)\dino Explorer 2015\Script) You can create your own batch file or you can use one of the batch files that are inside the zip file. create your own batch file Create a file named "Loadviews.cmd" and input the following content: NET STOP DinoMVS1 >> "C:\Program Files (x86)\dino 2015"\LoadViews.log DinoUtil.exe -load LoadViews >> "C:\Program Files (x86)\dino 2015"\LoadViews.log NET START DinoMVS1 >> "C:\Program Files (x86)\dino 2015"\LoadViews.log DinoMVS1 and LoadViews are suggested names. Replace it for yours. >> Don t forget (Stop all services before, run loadviews and start all services again) << Choose one of the batch files LoadViews and SwapLoadViews are examples of batch files that facilitate the loading of historical tables in DinoDB. Both batch file files access the ServiceList.ini file to obtain the service relation to stopped and subsequently initialized. The structure of the ServiceList.ini file is very simple, the name of the server where the service is installed and the name of the service. Below is the figure of the file in question. Dino Explorer Suite Installation Guide v

25 The batch LoadViews file performs the following activities sequentially: Stop all active services Run the DinoUtil utility to load historical information and initialize the xxxdata tables of the DinoDB database at the end of the process. Restarts all services that have been stopped. During the execution of the batch file, the real-time transfer of data between the MVS Server and the Server will be stopped. The batch SwapLoadViews file performs the following activities sequentially: Stop all active services Run the DinoUtil utility to swap the tables xxxdata to xxxdata1 and xxxdata1 to xxxdata Restarts all services that have been stopped. Run the DinoUtil utility to load historical information and initialize the xxxdata tables of the DinoDB database at the end of the process. During the first three activities, the real-time data transfer between the MVS Server and the Server will be interrupted, the downtime is very short, and the process of loading the historical tables is done from the xxxdata1 tables. Create a Schedule Task schtasks /CREATE /TN DinoLoad /RU "SYSTEM" /SC daily /ST 05:00 /TR "C:\Program Files (x86) \Dino 2015\LoadViews.CMD" We recommend you to set: "Manual start" "Set Recovery" Dino Explorer Suite Installation Guide v

26 Monitoring the Services Execute PERFMON.EXE Double-click Performance Monitor Select Add Counters, choice Dino Messaging and click Add button Dino Explorer Suite Installation Guide v

27 Switch to Report view and you will get a screen similar to the following: Dino Explorer Suite Installation Guide v