Author: <span class="vcard">Kenio Carvalho</span>
My Domino and Traveler is on the same machine using Linux.
1 - Install or upgrade the Domino server 9.0.1 FP3
2 - Install or upgrade IBM Traveler 188.8.131.52
3 - Configure Domino HTTP for SSL. This link was very useful for self cert.
4 - I am using iPhone. The easiest way to import the self cert was sending the cert by mail and then install the cert on the iPhone.
5 - Upgrade the Domino Directory ( http://www-01.ibm.com/support/docview.wss?uid=swg21699618). The current Domino Directory Template does not have a tab for IBM Verse.
6 - Download the IBM Verse App from the store and be happy :-)
According to man ssh:
Port to connect to on the remote host. This can be specified on
a per-host basis in the configuration file.
So you should be looking at:
ssh -p 1234 [email protected]
to connect to port 1234.
How to set :
1 - On the DMGR profile:
./wsadmin.sh -lang jython -user admin_user_id -password admin_password
2 -Type the following on wsadmin interface
3 - Do a checkout of LotusConnections-config.xml
4 - Change de following to true
5 Checkin the new LotusConnections-config.xml
6 - Sync and restart the nodes
I follow this tutorial, the setup is very simple but some problems arrive.
The Domino server have the FQDN domino.mydomain.com.br and the windows server server.mydomain.com.br. The SSO doesn't work.
I read the message Attempt by HTTP client to authenticate using Windows NTLM security is not supported on Domino console.
After the AD administrator setup the user dominostart, he issued the command SETSPN -a HTTP/domino.mydomain.com.br dominostart.
When the user try to access a url of the domino server the browser show a logon dialog but the title of the dialog show the windows server name (server.mydomain.com.br).
I asked the AD administrator to add another SPN SETSPN -a HTTP/server.mydomain.com.br dominostart
Everything works after a Domino restart. :=)
If you want to use Chrome as your browser you need to start Chrome with arguments
The Cognos wizard complete the CognosBI setup but Trasnformer not.
I set the logs to debug level and the messages does not help.
The problem was when the error appears the wizard roll back the installation of CognosBI removing everything from WebSphere.
After several reviews of the SLES libraries and Oracle client setup i made the setup only for CognosBI (previously i setup CognosBI + Transformer) successfully.
I try to open the cognos URL like http://server:port/cognos/servlet/dispatch/ext but the server doesn't send any response
Reading the cognos.log i found the following :
Initialization_SESS Initialization_REQ Thread-70 CM 6304 1 Audit.cms.CM StartService Warning
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. sealing violation:
package oracle.jdbc is sealed Runtime Exception stack trace: java.lang.SecurityException: sealing violation: package oracle.jdbc is sealed
I don't now why but the installer copy the orajdbc6.jar into Cognos.ear. I stop the cognos server, remove the orajdbc6.jar from the lib folder inside of cognos.ear and start the server.
The cognosBI works and Transformer was installed without problems.
The steps i follow
1 - Setup Cognos BI
2 - Stop the server and remove the orajdbc6.jar from the cognos.ear
3 - Start the Cognos Server
4 - Setup the Transformer
Check Enable native XMLHTTP support in the Advanced tab of the Internet Options dialog
Information from IBM TN 1698438
CLFRW0075W: Failed to load the index at startup, it may not have been created yetâ€�
The search index on one node was created/copied.
To solve the problem i just copy the index from another node.
2. IBM Connections 5.0 requirements for IBM FileNet for use with Connections Content Manager (CCM):
3. IBM Cognos Wizard for IBM Connections 5.0 Cumulative Refreshes (CRs)
4. Fix list for IBM Connections 5.0 CR2:
5. Updating the IBM Connections 5.0 databases to the required schema versions for Cumulative Refresh 2 (CR2):
6. New functions included in IBM Connections 5.0 CR2
7. Upgrade to IBM Connections 5.0 CR2 from IBM Connections 5.0 CR1 With Connections Content Manager (CCM)
See the full article here
Note that the JAR files may not be removed by a specific interim fix but the interim fix will remove all WebSphere Portal uses of those JAR files and the JAR files will be removed by a subsequent Cumulative Fix associated with that release.
These JAR files have been on the Portal classpath in many releases. They were never intended to be used by our customers but it is possible that they could be used by a customer's custom portlets or by a third party's custom portlets.
The specific JAR files that will be removed are the following:
The WebSphere Portal releases in which the removal takes place are:
WebSphere Portal V184.108.40.206
WebSphere Portal V220.127.116.11
WebSphere Portal V18.104.22.168
WebSphere Portal V22.214.171.124 (included in CF15)
WebSphere Portal V126.96.36.199
If you do not have any custom code or third party code that uses these JAR files you do not have to do anything as consequence of this removal.
If you do have custom code or third party code that depends on these JAR files to be in the Portal Server classpath then you will have to make a change. There are many options. You can simply add a copy of the JAR back into the WebSphere Application Server or WebSphere Portal classpath, add the JAR into the appropriate portlet WAR file (neither of which will protect you from the security vulnerabilities) or change your custom source code to use the new Apache HttpClient 4.3.6 JAR that does fix the security vulnerability. Changing the source code is the best option. Note that Apache HttpClient 4.3.6 is a complete rewrite of the library and there is no backward compatibility. Reference the Apache web site for more details.
From TN 1695483
External user are any users "marked" or "selected" as a external.
External users can:
- Only see Files and Communites that he/she has given access to
- See people in the community and business card (limited to some information)
- Search, but no public data will be returned.
The process is not complicated. The key is how to mark or select external users on your ldap. The options are;
1 - Map standard LDAP attribute for external users
3 - Use an LDAP branch to store external users.
I use the option 3 because on our LDAP external users are in another branch
I am using linux .
1 - First create another folder above /opt/IBM/TDI/V7.1.1 and copy the content of the TDISOL. I create with the nameTDISOLEXTERNAL
2- Edit map_dbrepos_from_source.properties and add a line
3 Edit profiles_tdi.properties and set the properties
4- Append a string to an external userÂ´s display name in map_dbrepos_from_source.properties
5 - Run collect.dns and verify the list of users. Do not run sync_all_dns.sh or you will inactivate internal users!
6 - run populate_from_dn_file.sh
7 - Only internal users with the role EMPLOYEE_EXTENDED can share content with external users. Add the role to the users using wsadmin
ProfileService.setRole("[email protected]", EMPLOYEE_EXTENDED)
Now you can collaborate with external users.
I found on the systemout.log the following
net.jazz.ajax.internal.util.TraceSupport warn The StyleSheet "com.ibm.lconn.core.styles.oneui3/base/applications/profiles"
To solve the problem shutdown the connections server and clean the temp folder of the websphere application server on all nodes.
Restart the server and everything must be ok.
Thanks to Michael Urspinger tip