Integration Tool
WEB - Installation |
Because "Integration Tool WEB" uses a central database to store all information
it's very easy to feed the database from different Integration Tool servers and/or
daemons. On every Integration Tool server you must configure the special database-handle
"WEB" to point to the tracking/web database (server).
Integration Tool WEB can
use SQL-server or Active-Directory user validation.
|
Requirements |
Integration Tool
WEB requires an SQLserver database where it can create the necessary tables.
Because Integration Tool WEB is essentially an ASP.Net website which visualises the
data in the (tracking) database you alse need to have an IIS (Microsoft
Internet Information Server) which supports ASP.Net.
|
Installation
/ Configuration |
- On every Integration Tool
server you plan to have access to Integration Tool WEB you need to configure the
"WEB" preset-database. You can do this with the "Manage
Databases" option in the "Options" menu of the "Configuration
Manager". Note that once you have configured this database and
you click "Ok" the necessary tables will automatically be
created in the database.
- To install
the Integration Tool WEB website use the following instructions:
- make sure
the WEB database has been created in the previous step
- if you do
not already have an ASP-membership database, create one by running
the following command: "{windir}Microsoft.NETFrameworkv2.0.xxxaspnet_regsql.exe"
and follow the onscreen instructions (use the defaults where possible)
- because the
Integration Tool WEB website will need to have access to the tracking-database
it is recommended to create a new user-account which will later be
used as the identity of an Application Pool (in which the Integration Tool WEB
website will run). Make this new user a member of the local "Administrators"
group. For added security you can change the policy of the account
to make sure the account can't be used to logon locally
- create a
new application pool using IIS Manager and make sure the ".NET
Framework version" is set to v4 and the "identity"
(advanced settings) of the application pool is set to the account
you created in the previous step
- Use the SQLserver
Manager to add a new login for the account you just created and make
sure it has datareader/datawriter privileges on the tracking database.
Also make sure you change the "User Mapping" of the login
and enable all "aspnet_...." roles for the "aspnetdb"
database and also enable datareader and datawriter.
- if you plan
to use active-directory authentication, make sure you create the following
user account in the default "Users" group: Integration Toolwebadmin
- in order
for the WebSetup installer to run correctly, make sure the following
features are installed on your system;
- on Vista/Windows7:
go to "Programs and Features" / Turn Windows Features
on or off / Internet Information Service / Web Management Tools
/ IIS6 Management Compatibility. Also make sure "ASP.NET"
is installed/enabled in the "World Wide Web-services"
section.
- on Windows
Server 2008: go into "Server Manager" and add the Role
Services for IIS 6 Management Compatibility
- using
the IIS Manager create an Application Pool of which the Integration Tool
WEB website will be a member. Change the identity of the Application
Pool to the account you created earlier.
- run the WebSetup
installer which is located in the "{Integration Tool installdir}WEBinstall".
During the setup select the Application Pool you created earlier.
- after the
Integration Tool WEB website has been installed it needs to be configured by
opening the "http://{yourserver}/Integration Toolweb" page
- now follow
the instructions to configure the database settings. If everything
was configured correctly you can use the default database-settings
(Use Logon Identity)
- once the
database-settings have been successfully configured you can click
"Continue" to logon to the tracking website. The default
password for the "Integration Toolwebadmin" account is "password1"
(when using SQL-server authentication)
- Now delete
the files "Install.aspx", "web.config.backup"
and "..binApp_Web_install.aspx.*" which are located in
the directory newly created "Integration Toolweb" website (c:inetpubwwwrootIntegration Toolweb).
Now you should
be able to access the Integration Tool WEB website (http://{hostname}/Integration Toolweb) and
view the different tracking Groups and Flows and other pages. The "Overview"
page contains an overflow of all the Flows in a Group. The "Details"
page shows more detailed information about a specific Flow in a Group.
On this page you will see the different Steps in a Flow and the status
of these Steps.
|
Update
Integration Tool WEB |
If
you have already installed Integration Tool WEB and want to install an update, you
don't need to run the installer package again, but you can simply extract
"WebUpdate.zip" (located in "{Integration Tool installdir}WEBupdate")
to your existing "c:inetpubwwwrootIntegration Toolweb" folder and overwrite
all existing files.
|
Search,
Connect RDP, Job Tickets |
The
"Search" page can be used to help you find things in your Integration Tool
configurations. Note that you first need to fill the database using the
"UpdateWebConfig" plugin. Typically you can run this plugin
every night in every daemon you are using to keep the configuration-info
in the database up-to-date.
If you want to be able to use the "Connect RDP" button which
is displayed in the search-results, you need to configure the rdp: mapping:
- copy the file
"RDP.js" which is located in {Integration Tool installdir}Tools"
to your "{windir}System32" folder
- edit the file
"RDP.reg" which is located in {Integration Tool installdir}Tools"
to make sure the paths inside the registry file are correct
- double-click
the "RDP.reg" file
If the security-settings
of your browser do not block this function, you should now be able to
use the "Connect RDP" button on the seach-results page.
The "JobTickets"
page can be used to submit data to pre-defined forms which can then be
processed by Integration Tool.
The "Monitor"
page can be used to view realtime logging information.
|