How do I manually include the users or groups for access to the Search and Discovery web page of Instant Archive Viewer for OCS?

It is possible to manually enter users and groups for access to use the Discovery section of Instant Archive Viewer for OCS which serves as an alternative to using the Directory picker shown below in ...itimarchiview/admin/index.aspx

Here is a the Directory picker to choose the Users or Groups in the Active Directory. We will be manually configuring this instead.

To manually configure these users for access to Discovery section...

1. First navigate to ...:\Inetpub\wwwroot\ITIMArchiveViews\Admin folder.2. Open DiscoveryConfig.xml in notepad:

The format for entering the user or group names is:

Domain Name\Display Name



Example:







Note: Be sure the "Domain Name\Display Name" is within "" start tag /GroupOrUser> end tag

Follow the instructions above to manually configure The extended search section for complete Archive Access as an Alternative to the AD Directory picker:



The location of the extended search configuration file is:
C:\Inetpub\wwwroot\ITIMArchiveViews\Admin\ExtendedConfig.xml

Here is an example:



For The Managers and Access groups section shown below:

Use Admanager.config located in the same directory: wwwroot.itimarchiveviews/admin/admanager.config. Open and edit in notepad.


Here are the tags, their format and uses:

1. AdGroups = Contains the GroupName,Managers, ManageUri, Members Uri and Members Tags

2. GroupName= The Group to Manage
Format: Domain name\Display name

3. ManageUri= the URI of the Manager
Format: 'user@domainname.com'

4. MembersUri = the member's Uri that will be managed
Format: 'user@domainname.com'

5. Members = the Display Name of the members of the group to be managed
Format: 'Display name'

How to enable SQL Server 2005 Express to allow remote connections for Instant Archive Viewer for OCS configuration

By default, SQL Server 2005 doesn’t allow remote connection so you have to enable it manually. If you try to connect to remote SQL Server without enable remote connection first, you’ll see one of these error messages.
“An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connection. ….

“Login failed for user ‘sa’. The user is not associated with a trusted SQL Server connection.

To resolve these problems, you have 2 majors task. One is to enable both SQL Server and Windows authentication mode on SQL Server and the other is to allow remote connection and SQL Server Browser.

• Check that you have allowed both SQL Server and Windows Authentication mode (If you’re not use Windows Authentication mode). For instance, user ‘sa’.
1. Login to SQL Server using SQL Server Management Studio Express on local SQL Server with Windows Authentication user. This will use Windows account to authenticate to SQL Server.
   
2. In Object Explorer, right click on the instance name and select Properties.
   
3. On the left, select Security and change Server authentication to SQL Server and Windows Authentication mode. If the choice is already selected, that means you have already allowed SQL Server authentication.
   
4. There’ll be an information window shows that you need to restart SQL Server to takes effect of the changes.
   
5. Right-click on the instance name again, select Restart to restart SQL Server service.
   
6. Select Yes.
   
7. Wait for service stop and start.
   
8. That’s it. You have enabled both SQL Server and Windows authentication so now you can login to SQL Server with your current Windows account or your created account.
• Check that you have enabled remote connection on SQL Server Surface Area Configuration
1. Open SQL Server Surface Area Configuration.
   
2. Select Surface Area Configuration for Services and Connections.
   
3. On the left side, expand your SQL Server instance -> Database Engine -> Remote Connections. On the right side, select Local and remote connections -> using both TCP/IP and named pipes.
   
4. On the left side, select SQL Server Browser -> Service.
   On the right side, if the startup type is Disable, you need to change to Automatic and click Apply and click Start button to start the service. Then, click OK.
   
5. You have finished configure. Now try to login to your SQL Server from remote computer using SQL Server authentication mode.
   
6. Login to SQL Server succeeded.
   
7. Now try testing the Connection in Instant Archive Viewer for OCS database settings tab on the Admin Page: ...itimarchiveviews/admin/index.asp:
8. 
   
   • Status: Test Connection Succeeded
   

References:
http://www.linglom.com/2007/08/31/enable-remote-connection-to-sql-server-2005-express/

Configuring OCS Archive Viewer with SQL 2008 Express

Trying to connect to SQL Server 2008 Express remotely without enabling remote connection first, may result in the following warning messages:

“Cannot connect to SQL-Server-Instance-Name

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server)”

“Cannot connect to SQL-Server-Instance-Name

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQLServer does not allow remote connections.(provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQLServer)”

“Cannot connect to SQL-Server-Instance-Name
Login failed for user ‘username‘. (Microsoft SQL Server, Error: 18456)”

To enable remote connection on SQL Server 2008 Express, follow steps below:

1. Open SQL Server Configuration Manager. Click Start -> Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL Server Configuration Manager.

2. On SQL Server Configuration Manager, select SQL Server Services on the left window. If the state on SQL Server Browser is not running, you have to configure and start the service. Otherwise, you can skip to step 6.

3. Double-click on SQL Server Browser, the Properties window will show up. Set the account for start SQL Server Browser Service. In this example, I set to Local Service account.

4. On SQL Server Browser Properties, move to Service tab and change Start Mode to Automatic. Therefore, the service will be start automatically when the computer starts. Click OK to apply changes.

5. Back to SQL Server Configuration Manager, right-click on SQL Server Bowser on the right window and select Start to start the service.

6. On the left window, expand SQL Server Network Configuration -> Protocols for SQLEXPRESS. TCP/IP protocol status is disabled.

7. Right-click on TCP/IP and select Enable to enable the protocol.

8. There will be a pop-up message stating that you have to restart the SQL Service to apply changes.

9. On the left window, select SQL Server Services. Select SQL Server (SQLEXPRESS) on the right window -> click Restart.

The SQL Server service will be restarted.

10. Now OCSAV can remotely connect to the SQL Server Express 2008.

11.Test the connection in Database Settings tab on the... itimarchiveviews/Admin/index.aspx Page

and Save.

Create a rename request in AdminP database and pull the same to BLA

Open Lotus Administrator, open the desired server by using 'File --> Open Server'

Browse to 'People', select the user you want to rename and then click rename on the right navigator.

In the next dialog, click on 'Change Common Name' and provide the servers's certifier ID.

Click 'OK' to the next dialog to confirm the expiration date.

Provide the new details of the user and click 'OK' to create a rename request in the AdminP database.

Provide the command 'Tell Adminp Process All' in the domino server console to immediately process the rename request you had created.
Once the rename request has been executed, a log document will be created under the rename request which will then be imported to the BLA using the action 'Import Requests from AdminP' in the BLA database.