I search for information on how to update the profiles photo from an ldap server. I found several information on how to use TDI to do a sort of imports on profiles.
I wrote this article on Connections Wiki like a How To
I search for information on how to update the profiles photo from an ldap server. I found several information on how to use TDI to do a sort of imports on profiles.
I wrote this article on Connections Wiki like a How To
Next week, I will be the instructor for a class of new Domino Designers. They will start from the basics
See how migration works
http://www.slideshare.net/ktree19/replacing-ltus-notes-heres-how-it-really-goes-down
LDAP filters consist of one or more criteria. If one than more criterion exist in one filter definition, they can be concatenated by logical AND or OR operators.
AND Operation:
(& (…K1…) (…K2…)) or with more than two criteria:(&(…K1…)(…K2…)(…K3…)(…K4…))
OR Operation:
(| (…K1…)(…K2…)) or with more than two criteria:(|(…K1…)(…K2…)(…K3…)(…K4…))
Nested Operation:
Every AND/OR operation can also be understood as a single criterion:
(|(& (…K1…)(…K2…))(&(…K3…)(…K4…))) means:(K1 AND K2) OR (K3 AND K4)
The search criteria consist of a requirement for an LDAP attribute, e.g. (givenName=Sandra). Following rules should be considered:
Equality: (attribute=abc) , e.g. (&(objectclass=user)(displayName=Foeckeler)
Negation: (!(attribute=abc)) , e.g. (!objectClass=group)
Presence: (attribute=*) , e.g. (mailNickName=*)
Absence: (!(attribute=*)) , e.g. (!proxyAddresses=*)
Greater than: (attribute>=abc) , e.g. (mdbStorageQuota>=100000)
Less than: (attribute<=abc) , e.g. (mdbStorageQuota<=100000)
Proximity: (attribute~=abc) , e.g. (displayName~=Foeckeler) Caution: ~= is treated as = in ADS environments !!
Wildcards: e.g. (sn=F*) or (mail=*@cerrotorre.de) or (givenName=*Paul*)
I made some VM´s using Windows 2008 R2 one year ago. I forgot the admin password.
I follow this steps to recover:
There are two known issues related to WCM with the CF4 installation for WebSphere Portal v8.0.0.1.
1.The CF4 installation fails if the Portal URI has been changed.
2. If you have disabled automatic syndication, it is re-enabled after CF4 installation completes.
ssue #1 – The CF4 installation fails during the post-install-configure step “CONFIG-WP-PTF-CF” if you have changed the Portal URI to something other than the default /wps. The failure occurs during the sub-script ‘run-wcm-admin-task’ here:
========================
run-wcm-admin-task:
[echo] VirtualPortalContext = , VirtualPortalHost =
[echo] Initialized: host my.portal.com vpContext
[echo] To call ConfigModuleClient: host my.portal.com vpContext
[ConfigModuleClient] Connecting to login address: customp://my.portal.com:10039/custom/wcm/login
[ConfigModuleClient] Connecting to task address: customp://my.portal.com:10039/custom/wcm/myconnect?MOD=data&processLibraries=false&taskType=import&input.dir=%2Fopt%2FIBM%2FWebSphere%2Fwp_profile%2FConfigEngine%2Fconfig%2Fwork%2Fct_import%2Fweb+content+templates&importLibrary=%24%7Bimport.library%7D with user name: uid=wpsadmin,o=defaultWIMFileBasedRealm
[ConfigModuleClient] No output will be shown while this task is running. Check the SystemOut.log for progress information.
— Exception Thrown —
/opt/IBM/WebSphere/PortalServer/wcm/prereq.wcm/config/includes/prereq.wcm_cfg.xml:3829: An exception occurred while executing the task: Header field ‘Set-Cookie’ is null. The login failed. Can not continue.
=========================
Solution – This is addressed in WCM APAR PM84880.
Issue #2 – If you have set the WCMConfigService property ‘connect.moduleconfig.syndication.inittasks’ to ‘false’ in order to disable automatic syndication, this property will be reset to ‘true’ after the CF4 installation completes.
Note: You can disable syndication by doing to each syndicator and disabling it there as opposed to setting this property
Solution – This is addressed in WCM APAR PM85264.
Both PM84880 and PM85264 have been packaged into a single download. You must apply it in conjunction with CF4 to avoid both of these issues:
– Add both CF4 and “8.0.0.1-WCM-IFPM84880-PM85264-CF04.zip” as repositories to IBM Installation Manager
– When prompted, select both for installation
This information is from TN1631948
Yesterday a costumer ask to update all servers because of this issue.
A URL manipulation security vulnerability has been found in the dojo module for WebSphere Portal versions 7.0.0.x and 8.0.
APAR PM64172 has been provided to address this issue.
The apar is included in CF14 for WebSphere Portal v7.0.0.1 and v7.0.0.2, and is available as an interim fix for WebSphere Portal v8.
This is a critical problem. When i simulate the attack i got the administrator password from security.xml
When you run cogconfig.sh to modify Cognos Transfomer you get the error:
13/05/2013,14:04:46,Err,java.lang.UnsatisfiedLinkError: JCAM_Crypto_JNI (/opt/ibm/Cognos/bin/libJCAM_Crypto_JNI.so: wrong ELF class: ELFCLASS32), com.cognos.crconfig.CRConfigFrame.initDataManager(CRConfigFrame.java:685)
The cause of this error was the JAVA_HOME pointing to the WebSphere JRE a 64 bit JRE.
Solution: Install 32 JAVA on the machine and point the JAVA_HOME to the 32bit JRE
Support for Sametime integration with ST Links has been dropped in iNotes 9.0. For this release, only Sametime Web Client integration via a Sametime Proxy Server will be supported. This will be the default setting when a new Server Configuration doc is created.
For the 9.0 release of iNotes, administrators will need to select “Sametime Web Client Integration” in the Server Configuration Doc and complete all additional fields with the appropriate information. This configuration change requires the deployment of a Sametime 8.5.2 IFR1 (with the latest hot fix), Proxy Server in addition to the Sametime Community server.
From TN 1633405
This error was throw CLFRQ0221E: Reference to directory services could not be retrieved.
Take the following steps to resolve this issue:
1. Login to the ISC.
2. Navigate to Security -> Global Security -> Single sign-on (SSO).
3. If “Interoperability Mode” is enabled, then you must specify the case-sensitive default names of “LtpaToken” and “LtpaToken2” for the
“LTPA V1 cookie name” and “LTPA V2 cookie name” fields respectively.
4. Synchronize the nodes & restart Connections.
[*Please note that the Help tips for these fields contain the incorrect case of “LTPAToken” and “LTPAToken2”.
See screenshots:
This defect is documented in the following APAR, which is due to be fixed in WAS FixPack 8.0.0.7:
The information is from TN 1635025