6 Configuration of ToolsNet applications
6.7 E-mail settings
6.7.4 Application configuration files
This section specifies the location and purpose of some of the files that are included in the installation package. Root:\Program Files\Atlas Copco AB\Email Module\TNEmail
This folder contains the files required by the event\email distribution service
config.xml Contains program settings
distribution rules.xml Contains rules, events and email addresses
unitsandpaths.xml Contains cached controllers and their location paths in reporting structures.
emails.xml List of email addresses
events.xml This file is updated from the ToolsNet database tables
TNEmail.log Support log for the email module
TNEmail.log4net Configuration file for log settings
9836 4181 01 49 (86)
Appendix A ToolsNet 4000 installation on Windows 2008 Server with IIS 7.0
To install ToolsNet 4000 on a Windows 2008 Server with IIS 7.0 a few steps must be taken:
• IIS must be installed and the IIS 6.0 scripting compatibility mode
• ASP.Net must be an allowed web server extension
Open the Server Manager
and click Roles in the structure window. If IIS is not present, click Add
Roles.
Select the Web Server (IIS) check box and click
Next to continue, and then click Next in the following dialog.
Configuration of ToolsNet applications Click Role Services in
the left menu and select the ASP.NET check box under Application Development.
Add the required roles and features by clicking
Add Required Role Services.
9836 4181 01 51 (86)
Click Role Services in the left menu and select the
• IIS Management Scripts and Tools
• IIS 6 Metabase Compatibility
• IIS 6 WMI Compatibility
• IIS 6 Scripting Tools
check boxes under Management Tools and IIS 6 Management Compatibility.
Review, and click Next to continue.
Configuration of ToolsNet applications Review all the
installation selections and click Install to proceed with the installation
The installation of IIS with ASP.Net and IIS 6.0 Compability mode.
Click Close and then close the Server Manager.
Open the Server Manager again to configure it.
9836 4181 01 53 (86)
Expand Roles -and Web Server (IIS) and click
Internet Information Services (IIS) Manager. In the connection window expand
Computer Name - Sites
and click Default Web Site
Click Advanced Settings…
In the Advanced Settings dialog box click Application Pool in the (General) list and click to select Application Pool.
Configuration of ToolsNet applications In the Application Pool
list, click Classic .NET AppPool.
Close the dialogs and the server manager.
IIS has now been installed and configured for installation of Toolsnet 4000.
9836 4181 01 55 (86)
Appendix B Transition from ToolsNet 3000 to ToolsNet 4000
ToolsNet 4000 can produce ToolsNet 3000 backup files in order to ensure a safe transition from ToolsNet 3000 to ToolsNet 4000.
• If only one server is available, the old data collection components must be disabled. The ToolsNet 3000 web application and database can remain on the server. The ToolsNet 3000 web application can be used to view data as usual.
• If a new server is available, then it is possible to let some controllers report to ToolsNet 4000 while other controllers still report to the old ToolsNet 3000 system. The data from the controllers reporting to the new system will be available in both ToolsNet 4000 and ToolsNet 3000.
• Note that the TNRestoreService application is distributed with ToolsNet W5 SR12 or higher. SR4 requires ToolsNet W5 SR13 in order to work.
B.1 Transition on one server
In short, the transition on one server is done by
1. Upgrade the server running ToolsNet 3000 to latest ToolsNet 3000 version.
2. Copy the Restore service files to a local folder and start the RestoreServiceManager. 3. Use RestoreServiceManager to disable the old ToolsNet 3000 data collection components.
4. Install ToolsNet 4000.
5. Use RestoreServiceManager to enable ToolsNet 4000 backup mode for ToolsNet 3000.
6. Data that was stored in ToolsNet 3000, before the transition, can be viewed in the ToolsNet 3000 web report application.
7. Data that is stored after ToolsNet 4000 is installed and put into backup mode can be viewed in the both the ToolsNet 3000 and ToolsNet 4000 web applications.
Configuration of ToolsNet applications
8. If ToolsNet 4000 encounters problems, it is possible to revert to ToolsNet 3000 and any data that was sent to ToolsNet 4000 during the startup period can be restored from the backup files into the ToolsNet 3000 system.
B.2 Transition with two servers
This section describes how to enable transition mode with one old ToolsNet 3000 server and a new ToolsNet 4000 server.
Note! The new data collection needs to be on a separate server if some controllers should be reporting to the new ToolsNet 4000 at the same time. The rest of the controllers report to the existing ToolsNet 3000 installation.
With this setup it is possible to test ToolsNet 4000 with a couple of controllers, and ramp up number of controllers during a period.
1. Upgrade the server running ToolsNet 3000 to latest ToolsNet 3000 version.
2. Install ToolsNet 4000 on the new server.
3. Enable ToolsNet 4000 backup mode for ToolsNet 3000.
4. Edit database connection string for TNRestoreService so that it points to the old installation.
5. Data that was stored in ToolsNet 3000, before the transition, can be viewed in the ToolsNet 3000 web report application.
6. Data that is stored after ToolsNet 4000 is installed and put into backup mode can be viewed in the both the ToolsNet 3000 and ToolsNet 4000 web applications.
B.3 IP-address vs. MAC-address
As default, ToolsNet 4000 uses MAC address as identifier of the reporting units. ToolsNet 3000 uses IP address.
The following settings are possible when doing transition:
• Default: ToolsNet 3000 running in IP-address mode / ToolsNet 4000 in MAC address mode.
• ToolsNet 3000 running in MAC-address mode / ToolsNet 4000 in MAC-address mode.
It is not recommended to run the combination with ToolsNet 3000 in MAC-address mode and ToolsNet 4000 in IP address mode.
B.4 Viewing ToolsNet 3000 data
To view ToolsNet 3000 data when the ToolsNet 3000 data collection is disabled, simply use the web browser as usual. The web interface will not be disabled.
9836 4181 01 57 (86)
B.5 Disable the ToolsNet 3000 installation
Start with upgrading ToolsNet 3000.
Note! ToolsNet 3000 must be upgraded to W5-SR10 or later.
1. Close all open applications. Make sure TNServerManager is closed.
2. Run the executable
RestoreServiceManager from the CD
Utilities\TNRestoreService. 3. Click Disable ToolsNet W5.
The ToolsNet 3000 executables will remain on the hard disk and be unregistered. They will not appear in the Services dialogue and will not be able to start or stop.
B.6 Install ToolsNet 4000
Install ToolsNet 4000 according to instructions in section 2 Installation.
B.7 ToolsNet 4000 backup mode
When ToolsNet 4000 runs in backup mode it will create backup files (.que files) that can be restored into ToolsNet 3000.
It is not recommended to run ToolsNet 4000 in backup mode for a greater transition period than 1-2 weeks, because of the amount of data produced in backup mode
Every hour (default but configurable) the active queue files will be converted into files readable by the restore service. The restore service will check the backup folder for new files every minute and restore them into the ToolsNet 3000 database.
1. In Windows Explorer create a folder where ToolsNet 4000 will store ToolsNet 3000 backup files.
For example C:\TN3000Backup\
2. Run the executable RestoreServiceManager from the CD Utilities\TNRestoreService
3. Press the button next to the QueueFileBackupPath and select the folder created in step 1.
This path must be available and writable from the server otherwise no backup files will be produced.
4. Press the button Enable Backup-mode. W7 will now be running in backup mode and the restore service is copied to the ToolsNet W5 folder, registered as a service and started automatically.
Configuration of ToolsNet applications
5. Verify that backup files are created by checking the folder specified in QueueFileBackupPath.
This folder should now contain three files:
• op_active.que
• pf_active.que
• pm_active.que
6. Verify that the TNRestoreService is started (In Windows: Administrative tools – Services – TNRestoreService)
Active queue files will default remain active for one hour. This value can be altered in the TNServer settings. After this time all active files are renamed and replaced with empty active files. The files that are not active can be restored into the ToolsNet 3000 database by the TNRestoreService.
B.8 Disabling ToolsNet 4000 backup mode after transition
When transition period is over, disable the backup mode.
1. Start the application RestoreServiceManager. 2. Press the button Disable Backup-mode.
Note! Data received after disabling backup cannot be restored into ToolsNet 3000.
B.9 Reverting to ToolsNet 3000 (W5)
1. Start the application RestoreServiceManager. 2. Press the button Enable ToolsNet W5(Go back)
The ToolsNet 4000 installation and database will remain on the server but the services will be disabled.
9836 4181 01 59 (86)
Appendix C Installing ToolsNet 4000 Oracle version
Note! SQL Server is the recommended database platform for ToolsNet 4000.
The Oracle version is to be installed by advanced installers approved by the ACTA SW Market Support team only and at customers where there’s an Oracle DBA available.
ToolsNet 4000 supports both Oracle 11g and Oracle 10g on 32-bit and 64-bit platforms. Oracle 9i is not supported.
C.1 Prerequisites
If Oracle is not installed, ask the DBA to install and set up the Oracle database server. The DBA do not have to set up any specific user, schema or table space. This is all taken care of by the installation program. Logon information for a user that has access rights to create users, schemas, tables and stored procedures is required.
C.1.1 Oracle Net client
Install Oracle Net client on the server for web applications and services if the database is on a separate server.
If the server for web and services is a 64-bit machine both the 32-bit and 64-bit Oracle clients must be installed. Order of installation does not matter but the environment path must be modified so that the 64-bit path comes before the 32-64-bit path.
Follow the Oracle installation guide to do this.
C.1.2 Setting up Net configuration (tnsnames)
Setup TNSNames for…. Enter the net name alias you have setup locally in your Oracle Net Configuration Manager. Enter a system administrator user and password.
Start the Oracle Net Configuration Assistant and click Local Net Service Name configuration. Click Next
Configuration of ToolsNet applications
Click Add to add a new net service name and then click Next.
Enter the Oracle Service name as it is configured on the Oracle server. In this example the Service is named tnora1.
Click Next.
Select the protocol used for database access.
Click TCP and then click Next.
9836 4181 01 61 (86)
Enter the host name. This is the name or IP-address of the database server.
Click Next.
Test the database connection to see if it is configured properly
Click Yes and then click Next to perform the test.
The default setting for user name and password should be invalid and you would get an error message like this.
Click Change Login to modify user name and password.
Configuration of ToolsNet applications
Change the user name and password to match the credentials you’ve been given by the Oracle DBA.
Click OK
.
When the login and setup is correct, you should be presented with a successful messagen Click Next to continue.
Give the configured net service connection a name. This is the name that you will refer to when making database connections in the ToolsNet installation.
It can be the same as the net service name, or set to something descriptive liketoolsnet.
Click Nextto save the configuration
.
9836 4181 01 63 (86)
Click
No. One net service name is enough for the ToolsNet installationClick Next.
Click Next to finish the configuration.
The content in the tnsnames.ora file should look like this after configuration.
TOOLSNET =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.46.25.149)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = tnora1) )
)
Configuration of ToolsNet applications
C.1.3 Registering Oracle.DataAccess.dll in the GAC
The Oracle.DataAccess.dll must be registered in the GAC in order for the ToolsNet applications to get access to the proper version. This is done on the services and web application server. If running on a 64-bit platform, registration must be done for both the 64-64-bit and 32-64-bit
1. To start the command prompt click Start,and then Run…. Type cmd and press ENTER.
2. Navigate to the 32-bit oracle client folder and the odp.net\bin\[version no] folder and run the
OraProvCfg.exe file with the full path to the Oracle.DataAccess.dll
3. Type OraProvCfg.exe /action:gac /providerpath:[fullpath to the data access dll]\Oracle.DataAccess.dll
9836 4181 01 65 (86)
C.2 Installation steps
Use the ToolsNet install.exe application to install ToolsNet, it will install databases and applications in the proper order.
Use the ToolsNet install.exe application to install ToolsNet, it will install databases and applications in the proper order.
In Select target database click Oracle and then click
Connect to database to set up a database connection.
This is the dialog for building a connection string.
Click Build… to continue.
Click Microsoft OLE DB Provider for Oracle and then click Next.
Configuration of ToolsNet applications
Enter the server name.
Note! This is the naming you gave in the Oracle Net Configuration setup. It is not the server name or IP address, neither the oracle Service name (even though it can be the same)
Check allow saving password and click test connection.
Click OK after a successful connection has been verified.
Click OK to finish the setup of building the connection string.
9836 4181 01 67 (86)
Click Install to start the installation programs.
Select which Oracle client version to use and then click
Ok.
The ToolsNet application installation will prompt for database server name or IP address.
Note! Enter the tnsnames for the database server here. The value should be prefilled from the verified connection you made in the ToolsNet Install.exe application.
Click Next to continue.
Configuration of ToolsNet applications
Use the suggested path for the script files or change location by clicking Change…
When the path is correct click Next, and thenclick
Install to begin the installation.
Note! Scripts can be extracted without running the full installation. This is specified in the section Error! Reference source not found. Error! Reference source not found..
Enter a folder path for the database files and click OK. Make sure to create the database on a disk drive with sufficient disk space.
Note! For data security reasons it is recommended to store the transaction log and data files on separate hard disk drives. To specify a different location for the transaction log and data files select the Advanced (select several folders) check box.
Note! Remember to check the Local install if the database installation is done on a remote server.
Note! If the remote Oracle database server is a Linux or Unix server, enter a unix file path here.
The database will be created. When the installation of the production database is ready, click Finish.
9836 4181 01 69 (86)
C.3 Database maintenance
Database maintenance consists of delete or purge of old data, and of backups. The installation scripts for both the DataCollection and the metadata database will add a few scheduled jobs to Oracles scheduler.
Backups is also a very important part of the database maintenance and database security. This has to be set up manually together with the Oracle DBA.
C.3.1 Delete maintenance
The following jobs have been added to the scheduler
Job Purpose Default values
DeleteMaintenance All results, graphs and events older than specified number of days to keep will be deleted. The deletion is done in six steps with the possibility to set different values for each step. The default values are the same for all steps
Step 1: Results – non safety critical Step 2: Results – safety critical Step 3: Graphs – non safety critical Step 4: Graphs – safety critical Step 5: Events
Days to keep = 100, Bulksize = 5000 (rows/transaction) Schedule is every day at 01:00
Job is not enabled
DeleteMaintenanceUnBound Graph
A job to delete all unbound graphs, i.e. traces without a result that have been sent to ToolsNet. This is usually a result of PM data drop commands.
Days to keep = 1 BulkSize = 5000
Schedule everyday at 02:35
Job is enabled.
DeleteMaintenanceLog Job to clear the delete maintenance log Bulk size 5000 Scheduled at 01:00 MetadataDeleteMaintenance Deletes all Logs, MaintenanceProgressEvents and
MaintenanceLogs that are older than the number of "days to keep" (see each step).
Days to keep = 100, Bulksize = 5000 (rows/transaction) Job is disabled
Schedule is every day at 01:00
The name, scheduling and details of the jobs can be listed by running the following command:
SELECT OWNER, JOB_Name, job_action, last_start_date, last_run_duration, repeat_interval, comments
FROM dba_scheduler_jobs WHERE owner = 'ATLASCOPCO_TOOLSNET';
The delete maintenance job is not enabled and should be configured with the proper settings before it is enabled. We recommend that SQLDeveloper version 3 or later is used to update the jobs but they can also be modified via sql scripts and calls to the dba scheduling procedures.
Look in your Oracle documentation for reference.
Configuration of ToolsNet applications
C.3.2 Backups
We recommend that the database is backed up according to Oracle procedures to secure the data. Backups should be setup together with the Oracle DBA.
C.4 Advanced Oracle installation
Note! Advanced Oracle installation is for experts only!
There are a few different scenarios on doing a ToolsNet installation 1. Regular installation
a. Local installation (Windows) b. Remote installation (Windows) c. Remote installation (Linux/Unix) 2. Modified installation
a. Changing the tablespace names b. Changing Database name
c. Multiple users (archive databases)
The regular installations are covered in previous sections for SQLServer and Oracle installation.
C.4.1 Running the database installation manually
Any advanced database installation will require that you first extract the database script files as described in section 1.4.1 Extracting database scripts in order to modify the files.
Make modifications as described in the section below and run the DBInstallWrapper.exe manually from the command prompt with the correct parameters.
DBInstallWrapper.exe Script=".\DataCollection\Oracle\DataCollectionWrappe r.cfg" DataBaseName=AtlasCopco_ToolsNet
9836 4181 01 71 (86)
C.4.2 Changing the database name
This section describes how to modify the database name for a first time installation of the database.
1. Modify the DataCollectionWrapper.cfg and change the
DATABASENAME=AtlasCopco_ToolsNet to DATABASENAME=NewDatabaseName1 2. Repeat the rename for the Meta database in ReportMetaDataWeapper.cfg
DATABASENAME=AtlasCopco_RF_Meta to DATABASENAME=NewDatabaseName2
3. Run the database installation manually from command prompt (Described in section C.4.1 Running the database installation manually) and use the NewDatabaseName1 and NewDatabaseName2 as the parameter for DataBaseName.
C.4.3 Archive database and multiple users
In order to have two ToolsNet databases within the same Oracle installation, one for production data and one archive database, you must:
1. Extract the database scripts files as described in section 1.4.1 Extracting database scripts.
2. Modify the Database name as described in section C.4.2 Changing the database name
3. Modify the script files where users and roles are created. (Search for Create users) all users names and all roles so that the archive users and roles gets new unique names in the Oracle instance.
4. Modify the grants to match the new roles.
5. Run the database installation manually from command prompt (Described in section C.4.1 Running the database installation manually).
There is no need to create an archive for the Report meta database, all logging of report progress and error messages is always done to the same database.
Configuration of ToolsNet applications
C.4.4 Changing the table space names
1. Extract the database scripts files as described in section 1.4.1 Extracting database scripts.
2. Modify the tablespace names by modifying all files that creates database files and tables. It is approximately 10 files to modify.
Use a tool like Programmers Notepad to do search and replace in multiple files at once.
3. Do this for each table space name you want to replace.
3. Do this for each table space name you want to replace.