|
| We have deployed the asynchronous module for our e-Learning system (Workplace Collaborative Learning).
The system was setup up on a Windows Server 2003 Std Ed. with Sp1. The server has 4 GB of memory and 2 dual core CPUs.
A couple of initial issues showed up:
1. During the installation process of the server, we chose the "Workplace Collaboration Services", "Workplace Documents", and "Workplace Collaborative Learning" options as per our license. But after installation we found that Mail_Server1 was starting alo
ng with Portal_Server when the startup script is initiated. When we explored the portal a bit, we saw that Web Conferencing, Messaging and various other components were also also deployed and seemed to be working. We were even able to create teamspaces. I
s such a situation considered normal? We've checked that the wpsadmin user had a welcome message in his mailbox. The Domino server for our deployment is only used for LDAP purposes for the time being.
2. After moving to an external web server (IBM HTTP Server v.6.2.1) as per the infocenter, we observed that both the portal and the learning login pages were able to connect from both the default port 9081 and port 80. We had no issues regarding logging o
n the WAS Admin Console whatsoever. After reading some more documentation we removed the virtual hosts for port 9081 from the WAS Admin Console. Updated the web plugin again and restarted the portal along with the HTTP Server. We were still able to access
the portal and the learning site from port 80 as expected and were now not able to access them from port 9081. But we noticed that when the Delivery Server comes in it still tries to gain access from port 9081. We then went to the settings tab of the lea
rning site and removed the port number from the hostname field for the delivery server, tested the connection and restarted the portal. Now the learning system was able to initially access the DS but still tried to open the learning content for the users
from port 9081. We rechecked all the parameters on the wpconfig.properties and dbbuild.properties files. But the only info regarding port 9081 was for the WpsAdminConsolePort parameter in wpconfig.properties. We have also rechecked all the properties file
s in the properties folder and resource files. What might have we done wrong?
3. The infocenter and several other documentations have information regarding the removal of the sign-up link. But the method seems to only remove the link from the default Workplace theme. How could we remove the link from another theme?
4. We want to force our users to change there password after their initial logon attempt. Thus we made the required adjustments on domino and tested the configuration by accessing domino via its HTTP service (using another port). The adjustments were work
ing well, but when trying the same thing when logging on to the Portal or the Learning site, the user was able to login without changing his/her password.
Note: We have enabled write access to LDAP for this purpose.
5. We tried signing up a new user from within Workplace and noticed that the user name field for the users person document in domino was using the shortname and not the fullname. The same issue arouse when the users tried to change their passwords from th
ere profiles setting; these users were created from within domino and had there full name in their user name field. But once they changed their password their user name field was condensed to their shortname again (eg. wsmith/Acme). Anyone have suggestion
s?
Sorry for the long post, just trying to provide sufficient detail to ease troubleshooting.
|
|