This document provides instructions for setting up a secure Lotus Domino server playground in one hour. It outlines installing and configuring Domino server and administrator client software, securing the server by configuring various security settings, creating internet site documents for web and SMTP access, and performance tweaks like disabling unnecessary server tasks. The goal is to have a secure one-server Domino environment for development and testing purposes.

1. BP108 Admin for the Developer -- Build and Secure Your Own IBM Lotus Domino Server Playground in One Hour! Jess Stratton | IBM Lotus Domino Consultant, Solace

3. Has worked with Lotus Notes â /Domino since R4.x, ~10 years.

4. Speaks at The View’s Admin and Developer conferences.

5. Has written articles for Group Computing/E-Pro Magazine.

6. Hosts the group blog at LotusUserGroup.org (blog with me!)

7. Has submitted apps to OpenNTF.org.

8. Co-hosts the 1352 Report podcast on industry news.

9. AND – I’m an administrator AND a developer! A great thing about developing and administrating together: You can write agents to do all your Administration tasks!

11. You want to set up a developing playground at the office…

12. BUT…

13. All the servers you’ve ever developed for have been installed and are in place already!

17. Launch/install setup file

18. Configure the newly installed Lotus Domino server

19. Start Domino

20. Install and configure the Administrator client

21. Secure and further tweak the Domino server

22. Setup a firewall for external access to the Domino server

23. Register our test subjects. I mean, er, users Agenda slide

25. Administrator Client setup

26. Configuring Domino

27. Configuring a firewall for external access

28. Registering users

29. Addendum: Playing safe with existing (production) servers

30. Installing Lotus Domino 8.5

32. Basic PING test is fine, but make sure they can TALK!

33. If using Virtual PC/VMware, do ping test between host and client. PREREQUISITES

35. Download from Passport Advantage, double-click!

45. Enter Organization name, i.e.. Playground

46. Enter Domain name, i.e.. MyDomain Text slide with inset photo

49. Domino will now create databases, and you’re ready to launch the server!

51. The first time Domino starts, it creates databases, starts services, and checks stuff like host names.

52. It may take a few minutes, and log a few errors. Just let it start! For example, it may be trying to start services whose partner databases haven’t been created yet.

53. Once it’s settled down (and the server stops sounding like a percolating coffee maker) type ‘q’ to bring down the server, and then start it up again.

54. Lotus Domino Administrator Client Setup

58. Put in the Administrator name you used and the Domino server name when you registered.

60. We won’t tell anyone. Promise.

62. Configure your Location document to automatically switch to your Playground ID file.

63. So never the twain shall meet – Configure the Connection document to only work for THAT ID file and location document.

64. Configuring Lotus Domino (using the Domino Administrator Client)

66. Maximum Internet name and password should be 'Reader', unless you want to use Web Admin, and then it should be 'Editor'. Text slide with pie charts

83. Add your Domino server IP address in “Allow messages only from the following internet hosts to be sent to external internet domains”.

90. Add Anonymous with ‘no access’

97. Local primary Internet domain: Enter any Internet domains (ie. '.com' email addresses you are using with this Domino server).

98. Save and close the document.

100. Shutting off unnecessary server tasks.

108. HTTP (if not running web server)

109. SMTP (if not running SMTP server)

110. LDAP

111. IMAP

112. Design (if you don’t want your templates updated automatically)

114. Use Notes.ini params in the configuration file, or

120. “Web”

122. Give name and description.

123. Organization should be your Certifier name.

125. If using a POP forwarder, such as PopWeasel, enter ‘localhost’ here.

128. Give name and description.

130. (To set up SSL, see the Domino Administrator Help File, “Setting Up SSL on a Domino Server”.)

133. Mail/mymailfile.nsf

136. Server document->Ports tab->Internet Ports tab->Web:

137. TCP/IP Port Number: Change 80 to 8081.

138. Issue console command “Tell http restart”

140. Template server: Your playground server (show advanced templates)

141. Use template: Domino Web Server Configuration

142. Title the database “Domino Web Configuration”, with the filename “Domcfg.nsf”. (these aren’t negotiable  )

144. Configuring a Firewall for External Access

146. The Username and passwords to get into the Firewall or Router.

148. You don't have to do this if they aren't accessible outside your internal network.

150. SMTP: 25

151. Notes Client: 1352

152. HTTP: 80

153. HTTPS (SSL): 443

154. LDAP: 389

155. Sametime: 1516

157. Set the Start and End range (they can be the same).

158. Set the IP address to the IP address of the Domino Server.

159. Do this for each port/service you need!

160. Registering Users

162. And, it will take up a lot of hard drive space too, if this is a home machine.

165. Cancelled 80’s TV shows.

166. Hitchhiker’s Guide characters. Why? Because cool names = cool playground = people will think you’re cool. 

169. Paste the values all the way down the entire column. Instant passwords!

170. Use =LEFT(A1,1)&B1&1 to add ‘1’ if a number is required.

171. For the name of the ID file, use =LEFT(A1,1)&B1&”.id”

173. Rename the extension to .TXT

174. Open the text file (in Notepad).

175. Find and replace all ‘,’ with ‘;’.

176. Our text file is complete!

178. Choose cert.id

179. Click ‘Advanced’

182. Click “Register All”

183. Addendum: Playing safe with existing (production) servers

186. For mail routing scenarios, Adjacent Domain documents are needed, too.

188. One domain, same NNN No connection documents required! DomainA NNN A Domino Directory A names.nsf

189. One domain, two Notes Networks: Connection document required to route between NNN. DomainA NNN A NNN B two connection docs Domino Directory A names.nsf

190. Two domains, two NNN. Cross-certification & connection docs required cross-certification connection docs DomainA NNN A Domino Directory A names.nsf DomainB NNN B Domino Directory B names.nsf

193. Certifier

194. Notes Named Network

195. Contact me with questions! (good jokes always accepted graciously, too) JESS STRATTON SOLACE EMAIL: jstratton@solacelearning.com BLOG 1: www.mattandjess.net BLOG 2: www.momelettes.com Twitter: @NerdGirlJess

196. Your turn!