LOTUSCONNECTIONS.org

In our situation we have one was profile with 6 servers instances
on it, one server instance for every part of Lotus Connections.

Whenever we want to use a checkOut config task for server2
( or server3 till server6 ) we have to do this on the SOAP port of server1.

example:
./wsadmin.sh -lang jython -user wasadmin -password ********** -port 8880
execfile(“communitiesAdmin.py”)
CommunitiesConfigService.checkOutConfig(‘/tmp’, ‘con10Node01Cell’)

For changes on a part of Lotus Connections that does not require
you to use the checkOutConfig task you can do this directly at
the SOAP port of that server instance.

example:
./wsadmin.sh -lang jython -user wasadmin -password ********** -port 8883
execfile(“communitiesAdmin.py”)
CommunitiesService.purgeIndex()
CommunitiesService.startIndexing()

At my company e-office, we were working on a customization in
Lotus Connections for one of our customers.

Because every change regarding the lay-out ( editing a *.HTML,*.CSS,*.JS file )
requires a restart of the specific EAR ( Activities , Blogs, etc ) I made
a script in WSadmin python so we could simplify this process.

Now we can restart an EAR file with a single command line instead
of clicking yourself senseless through the WASadmin web interface .

FILE restart_activities.py

appName=’Activities’
server=’server1′

cell=AdminConfig.list(‘Cell’)
cellname=AdminConfig.showAttribute(cell,’name’)
nodes=AdminConfig.list(‘Node’,cell)
nodename=AdminConfig.showAttribute(nodes,’name’)
appManager=AdminControl.queryNames(‘type=ApplicationManager,cell=’+cellname+’,node=’+nodename+’,process=’+server+’,*’)

AdminControl.invoke(appManager, ’stopApplication’,appName)
AdminControl.invoke(appManager, ’startApplication’,appName)

!FILE

wsadmin.bat -lang jython -user wasadmin -password ***** -port 8880 -f .\wsadmin_scripts\restart_activities.py

Create a *.py for every part of Lotus Connections.

We configured our Lotus Connections setup to use our Domino LDAP
as the user repository.
In this Domino LDAP we have a primair and secondary addressbook.

When configuring profiles to use our Domino LDAP we discovered that
profiles wouldn’t read any entries that were in the secondary address book.

But after some experimenting with the settings in the file profiles_tdi.properties
we found out that when we leave the parameter source_ldap_search_base
empty we were able to retrieve the users from the secondary address book.

Strange issue but for now we can work with it.