IBM AD04BML Installation Guide - Page 104

Checking server information in profile documents, In the Action bar, click Library Administration

Page 104 highlights

5. Open the Ports tab, then open the Notes Network Ports tab. Verify that the Net Address in the TCPIP line is correct, and that it matches the fully qualified Internet host name that you verified in step 4. 6. Open the Internet Protocols tab, then open the HTTP tab. Verify that the "Host name(s)" field contains the fully qualified Internet host name that you verified in step 4. 7. Open the Ports tab, then open the Proxies tab. Verify that the proxy settings for the server are correct. Then, from an operating system shell on the server, perform a "ping " to make sure that the proxy server is accessible. Note To avoid errors, you may need to clear all proxy setting fields, including "No proxy for these hosts and domains." 8. Open the Security tab, then do the following: • If the "Only allow server access to users listed in this Directory" field is set to "Yes," verify that the server's name is explicitly listed in the "Access server" field directly below it. • Verify that the server name and the Domino.Doc Site Administrators group are specified in the "Run unrestricted LotusScript/Java agents" field (if you are using a Domino 5 server) or in the "Run unrestricted methods and operations" field (if you are using a Domino 6 server). 9. Save and close the server document. Checking server information in profile documents To check that the Document Manager server name is specified correctly in the appropriate profile documents, follow these steps: 1. Using an administrator ID (a Notes ID that is a Domino administrator), open the master copy of the library where the problem occurs. 2. In the Action bar, click Library Administration, then click System Profile. 3. From the File menu, choose Document Properties. 4. In the InfoBox, click the Fields tab, then scroll down to HTTPHostName. Verify that the field value exactly matches the fully qualified Internet host name that you confirmed in step 4 of "Checking server configuration." 5. Close the InfoBox, then press ESC to close the System Profile. 6. In the Action bar, click Replication. 7. Select the document for the replica server where the problem occurs, then from the Edit menu, choose Properties. 100 Document Manager Installation Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

5.
Open the Ports tab, then open the Notes Network Ports tab. Verify that
the Net Address in the TCPIP line is correct, and that it matches the fully
qualified Internet host name that you verified in step 4.
6.
Open the Internet Protocols tab, then open the HTTP tab. Verify that the
“Host name(s)” field contains the fully qualified Internet host name that
you verified in step 4.
7.
Open the Ports tab, then open the Proxies tab. Verify that the proxy
settings for the server are correct. Then, from an operating system shell
on the server, perform a “ping <proxyserver>” to make sure that the
proxy server is accessible.
Note
To avoid errors, you may need to clear all proxy setting fields,
including “No proxy for these hosts and domains.”
8.
Open the Security tab, then do the following:
If the “Only allow server access to users listed in this Directory” field
is set to “Yes,” verify that the server’s name is explicitly listed in the
“Access server” field directly below it.
Verify that the server name and the Domino.Doc Site Administrators
group are specified in the “Run unrestricted LotusScript/Java agents”
field (if you are using a Domino 5 server) or in the “Run unrestricted
methods and operations” field (if you are using a Domino 6 server).
9.
Save and close the server document.
Checking server information in profile documents
To check that the Document Manager server name is specified correctly in
the appropriate profile documents, follow these steps:
1.
Using an administrator ID (a Notes ID that is a Domino administrator),
open the master copy of the library where the problem occurs.
2.
In the Action bar, click Library Administration, then click System Profile.
3.
From the File menu, choose Document Properties.
4.
In the InfoBox, click the Fields tab, then scroll down to HTTPHostName.
Verify that the field value exactly matches the fully qualified Internet
host name that you confirmed in step 4 of “Checking server
configuration.”
5.
Close the InfoBox, then press ESC to close the System Profile.
6.
In the Action bar, click Replication.
7.
Select the document for the replica server where the problem occurs,
then from the Edit menu, choose Properties.
100
Document Manager Installation Guide