View source for BPC RiskManager - Test a Client Connection

=Introduction=
Finally, if you are using a security mode other than the “maintained by RiskManager” mode, you should restart the RiskManager Dataserver client and switch to the security mode you will be using (eg. LDAP or NT Groups) and test that the connections from the various clients are working from remote computers.


The installation is not complete until you can successfully test a client application.  This will ensure that you are ready to distribute the client components and can begin to ‘roll-out’ your new Risk Management solution.


If this is a fresh install, and you have set up the rootadmin user ID, you should use the user id linked to the rootadmin to do this test (and at the same time create the first real Risk Administrator user account – per the earlier instructions).


=Test 1: Test Connection From Internet Explorer=

 ''This test is relevant if you will be using the browser plugin  client.''


* T1.1: Open Internet Explorer and point your browser to the Risk Manager intranet site


'''Comment:''' If the virtual web directory has security set to ‘Integrated Windows authentication’ then loading the page will test its correct activation.


* T1.2: Verify download of ActiveX controls


'''Comment:''' The default web page contains ActiveX controls.  These controls are the Risk Manager client components.  To enable distribution of Risk Manager’s client components using a web browser the browser needs to accept digitally signed ActiveX controls from the Intranet zone (allowing download and run) or other zone ass appropriate to your usage.  This is the default security value for Internet Explorer when installed.


* T1.3: Verify correct settings of ActiveX control parameter values

'''Comment:''' The application server name and available connections in the connection screen are assigned from the ActiveX parameter values entered during configuration.


* T1.4: Verify authentication of the connecting network user

'''Comment:''' Each system user must be setup and assigned access in the Risk Manager database.  If  the user testing the program has not been assigned access then this test can be concluded as successful since all configurations can be verified as correct at this point OR you will need to add database records to tables: RESOURCES & USERS to assign system access.


The network user must pass the access requirements of the selected method of assigning secure access:
<ul>
<ul>
<li>If either of the NT group methods are applied then the network user must be a member of the correct NT group.
<li>If ‘Application Access’ method is applied the network user must have a record in the RESOURCES table set with the correct NETWORKED_USERNAME value and have field ASSIGNED_ROLE set to a valid Risk Manager role.
</ul>
</ul>



=Test 2: Test Connection From Risk Manager Windows Program=


In V6.1.9 and above non-browser client no longer requires an install set.  The client can be merely copied to a target computer and run.  If you wish to create menu buttons and desktop shortcut links, this can be done manually or using the provided install set.  The installset version and the exe client are the same application.


* T2.1: Verify correct operation of the method of delivering the non browser client


'''Comment:''' The non browser client can be delivered in two ways:
<ul><ul>
<li> The install set is downloaded and automatically installed silently for new users when they connect to the network.
<li> New users are required to install the program themselves either from a shared network location or from CD.
</ul></ul>


If using networking software to ‘push’ the install set out automatically to new users please verify that the ocx control is registered to the interactive user.


* T2.2: Verify authentication of the connecting network user


Run program ‘BPC RiskManager’ from the Start menu.  Enter selections for Risk Server Computer Name and Database Connection (optional).  Click ‘Connect’.


'''Comment:''' Each system user must be setup and assigned access in the Risk Manager database.  If  the user testing the program has not been assigned access then this test can conclude as successful since all configurations can be verified as correct at this point OR you will need to add database records to tables: RESOURCES & USERS to assign system access.


The network user must pass the access requirements of the selected method of assigning secure access:
# If either of the NT group methods are applied then the network user must be a member of the correct NT group.
# If ‘Application Access’ method is applied the network user must have a record in the RESOURCES table set with the correct NETWORKED_USERNAME value and have field ASSIGNED_ROLE set to a valid Risk Manager role.






=BackLinks=

{{#dpl: linksto={{FULLPAGENAME}} }}