OES2SP2 SLES10 SP3

[DrumDude]

Hi,
I have been working in the imanager queue to solve issues with tomcat
and imanager apps,iPrint etc.
The server edirectory is OK as well as imonitor and remote manager
Something is just zonked with imanager and tomcat.
I want to start over. Unless someone is in the know.

It is Transfer ID destination server.

How do I start from scratch.
- remove eDirectory from the server
- remove all of OES2SP2
- re-install OES2SP2

I have re-installed the packages it does not solve this issue. Even
though there was no errors in the original installation.

I hope it does not need a partition (as it is a transfer ID source
server) to solve these iMananger/Tomcat issues.

I used this media: on this server X3650 series Model 7979-AC1
OES2-SP2a-x86_64-CD1.iso 658.7 MB (690759680)
SLES-10-SP3-DVD-x86_64-GM-DVD1.iso 2.8 GB (3030702080)
SLES-10-SP3-DVD-x86_64-GM-DVD2.iso 3.0 GB (3238070272)

[Joseph Marton]

On Fri, 29 Jan 2010 20:53:33 +0000, DrumDude wrote:

> How do I start from scratch.

Honestly, the best way is to wipe the server completely. If you just
wanted to return it to being SLES I'd say it'd be safe to uninstall all
OES2 packages, but if you still want OES2 on this machine I would
recommend reformatting. You'll want to remove it from the tree first,
though, which I believe is done through ndsconfig. Best to ask in the
eDir forums. Once it's out of the tree the server can safely be wiped.

--
Joe Marton
Novell Knowledge Partner

[DrumDude]

I think you are correct; as I have safely removed eDir from the Tree and
OES-Install from Yast2; rebooted; tried to run OES-Install; stated it
was not present; re-ran OES-Install over again,Imanager, iPrint, NSS etc.
Still iManager would not work; it is hooked in all over. Or there is a
bug in iManager and iPrint on a "Transfer ID Migration Server"

Everything else works; NSS, migrating volumes, pureftp, NRM and iMonitor.

I do remember in OES infancy that iManager required a r/w of root. I am
going to try that for sanity sake.
Else take your advice start over and format like you said.

Joseph you have been around Novell as long as I have or longer.;)
Thanks
Jeff

[DrumDude]

Update:
Solved: So I started searching JAVA and iManager and Bingo.
Thanks to this chap Lewis G Rosenthal.
If you search "Failed re-install of iManager" in this iManager newsgroup
then you will find the solution.
What a pain and waste of hours but I am happy that I do not have to
re-install. My hair is whiter.;)

Solution Snapshot more details if you review and search thread above.

Here are the security files in concern.
In my case it was exactly the 64bit issue. So edit
/usr/lib/jvm/java-1_5_0-ibm-1.5.0/jre/lib/security/java.security
Verify , match up or paste in.
security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
security.provider.2=com.ibm.crypto.provider.IBMJCE
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.sasl.IBMSASL
security.provider.60=sun.security.provider.Sun
security.provider.61=com.sun.net.ssl.internal.ssl.Provider

rcnovell-tomcat5 restart
and you should be in business.

Note: security files listing on 64bit.
/usr/lib/jvm/java-1_5_0-ibm-1.5.0/jre/lib/security/java.security
/usr/lib64/jvm/java-1_5_0-ibm-1.5.0/jre/lib/security/java.security