Dani's Middleware

1. Create a digital certificate Windows XP: Start -> All Programs -> Microsoft Office Tools -> Digital Certificate for VBA Projects Follow the instructions to create a certificate. 2. Sign the Macro In Outlook: Tools -> Macro -> Visual Basic Editor. In the Project Explorer, select the project you want to sign. Click Tools -> Digital Signature. Click Choose, select the certificate, click OK twice. Save. 3. When you open or run the macro, you will get a security warning. Check "Always trust macros from this source". Thanks to that unknown guest: http://www.pcreview.co.uk/forums/showpost.php?p=2488705&postcount=3

If you already configured the WPM and then found out that it is implemented in the ISC (What a bad idea!), then you have to unconfigure the WPM: # /opt/PolicyDirector/sbin/amwpmcfg -action unconfig -interactive Then unpack the iscwpm.war (/opt/PolicyDirector/java/export/pdwpm/iscwpm.war): # /opt/WebSphere/AppServer/java/bin/jar xvf /tmp/iscwpm.war Modify ibm-portal-security.xml: old: new: Repack the iscwpm.war (remove the copy of your original /tmp/iscwpm.war first) and put it into place again: # /opt/WebSphere/AppServer/java/bin/jar cvf /opt/PolicyDirector/java/export/pdwpm/iscwpm.war /tmp/* Reconfigure the WPM: # /opt/PolicyDirector/sbin/amwpmcfg -action config -interactive Then you can give your WPM Adminperson the role wpm-user within the ISC. Then he/she can see everything, but can only do changes in WPM. IBM link: http://www-01.ibm.com/support/docview.wss?rs=638&context=SSPREK&q1=6.1+role&uid=swg21307731&loc=en_US&cs=utf-8&lang=en

Solution: Use another Java. I found this at IBM pages: Certain versions of Sun Java are incompatible with tfimcfg. The incompatibility causes the following error: HPDAZ0602E Corrupted file: Insufficient information to contact Policy ServerThe problem occurs because the Sun JRE is unable to read the keystores generated by the Tivoli(R) Access Manager PDJrteCfg. When this error occurs, you should either use an IBM(R) JVM or else apply the latest JRE patches from Sun. If the problem persists after applying the patches from Sun, use an IBM JVM for the configuration. I had the problem unconfiguring the WPM of TAM for e-business. So I used the java in /opt/WebSphere/AppServer: . /opt/WebSphere/AppServer/bin/setupCmdLine.sh