Difference between revisions of "HowTos/Advanced omldapsync"
From Scalix Wiki
(→Known Issue in scalix v.12.0) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [How-Tos] -> '''Advanced omldapsync''' | + | [[Scalix Wiki]] -> [[How-Tos]] -> '''Advanced omldapsync''' |
== sync.cfg Tips & Tricks == | == sync.cfg Tips & Tricks == | ||
=== Mapping Tables === | === Mapping Tables === | ||
==== Predefined Custom Mappings ==== | ==== Predefined Custom Mappings ==== | ||
* '''!CUSTOM=IM_LOCAL_DOMAIN''': This custom mapping manages the correct mappings and selections of attribute values when exporting contact records to Exchange environments. Note that this has some special behaviour for agreement type 22 (Bidirectional Active Directory), which has not been supplied. If the agreement type is 22, special mapping behaviour will use attribute names '''mail''' instead of '''rfc822mailbox''', '''targetAddress''' instead of '''Target-Address''' and '''proxyAddresses''' instead of '''otherMailbox'''. | * '''!CUSTOM=IM_LOCAL_DOMAIN''': This custom mapping manages the correct mappings and selections of attribute values when exporting contact records to Exchange environments. Note that this has some special behaviour for agreement type 22 (Bidirectional Active Directory), which has not been supplied. If the agreement type is 22, special mapping behaviour will use attribute names '''mail''' instead of '''rfc822mailbox''', '''targetAddress''' instead of '''Target-Address''' and '''proxyAddresses''' instead of '''otherMailbox'''. | ||
| + | |||
| + | |||
| + | === Known Issue in scalix v.12.0 === | ||
| + | In v.12.0 omldapsync is incompatible with any JRE v. 1.6 and v. 1.7, currently just v. 1.5 is supported), so you need to | ||
| + | * download and install JRE 1.5 | ||
| + | --- Java 1.5: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html#jdk-1.5.0_22-oth-JPR | ||
| + | |||
| + | * change JAVA_HOME in /var/opt/scalix/<instance>/s/ldapsync/<configuration name>/sync.cfg | ||
| + | <code>JAVA_HOME=/{YOUR PATH TO ORACLE JAVA BINARY GOES HERE}/</code> | ||
| + | * add JAVA_HOME line in /etc/opt/scalix-tomcat/scalix-tomcat.conf | ||
| + | <code>JAVA_HOME=/{YOUR PATH TO ORACLE JAVA BINARY GOES HERE}/</code> | ||
| + | * restart tomcat service | ||
| + | * now you can use omldapsync | ||
Latest revision as of 14:30, 22 November 2013
Scalix Wiki -> How-Tos -> Advanced omldapsync
Contents
sync.cfg Tips & Tricks
Mapping Tables
Predefined Custom Mappings
- !CUSTOM=IM_LOCAL_DOMAIN: This custom mapping manages the correct mappings and selections of attribute values when exporting contact records to Exchange environments. Note that this has some special behaviour for agreement type 22 (Bidirectional Active Directory), which has not been supplied. If the agreement type is 22, special mapping behaviour will use attribute names mail instead of rfc822mailbox, targetAddress instead of Target-Address and proxyAddresses instead of otherMailbox.
Known Issue in scalix v.12.0
In v.12.0 omldapsync is incompatible with any JRE v. 1.6 and v. 1.7, currently just v. 1.5 is supported), so you need to
- download and install JRE 1.5
- change JAVA_HOME in /var/opt/scalix/<instance>/s/ldapsync/<configuration name>/sync.cfg
JAVA_HOME=/{YOUR PATH TO ORACLE JAVA BINARY GOES HERE}/
- add JAVA_HOME line in /etc/opt/scalix-tomcat/scalix-tomcat.conf
JAVA_HOME=/{YOUR PATH TO ORACLE JAVA BINARY GOES HERE}/
- restart tomcat service
- now you can use omldapsync
