We are installing IdM 7.1 with Websphere 6.0 We went through the install and everything imported correctly. We logged into WAS 6 to start iDM and WAS then abruptly terminated.

We used iDM 7.1 against WAS 6 with an Oracle 10g backend.

WAS from this point on refuses to start. In order to start WAS we have to rename the iDM directory ?.\idm.ear\idm.war to ?.\idm.ear\idm.war.old, then start the WAS service.

IdM 7 with WAS 6 and Oracle 10g works fine.

Help!

Steve Hulme

 

 

We have seen the same behavior when installing IDM 7.1 on MS Windows/IBM Websphere 6.0.2.15. Have you been able to make any progress on this issue?

Regards,

Byron

 

 

Steve,

What platform are you running on? We are also seeing the same issue with IdM 7.1 crashing WAS 6.0.2.17.

We're running on Windows Server 2003 Standard, WebSphere 6.0.2.17 with JRE 1.4.2. Our backend repository is MS SQL Server 2005.

- Jason

 

 

We have the same problem--idm7.1 update 1 and 7.1 crash WAS brutally. For info the 7.0 does appear to work (as does the 6.0).

Also as part of the investigation found that 7.1 crashes in tomcat with the ibm jre 1.4.2....

 

 

Hi,

I dont have any problems with WAS 6.1.0.9 and IDM 7.1 with Oracle 10g backend. and the directory structure of idm is idm_war.ear/idm.war

 

 

forgot to mention, it has JRE 1.5

 

 

Thanks for the info.

Our env is WAS 6.0.2.25, ibm jre 1.4.2, windows. Even with a direct jdbc mysql repo it crashes. Though our goal is to deploy a WAS data source Oracle 9i repo.

For info, with the WAS 6.1 which works for you, do you have a direct jdbc backend or are you using a WAS data source ?

 

 

We also faced Websphere 6.0.15 and 6.0.17 crashes with IDM 6.0.

Eventually found this was a regression of those particular FixPacks in
logging i18n logic : when the current Locale is invalid WAS is unable to
log anything and just crashes without any error message.

WAS is really the worst app server on the market !

 

 

I am using jdbc to connect to the repository. I did face a problem once, I was not able to connect to the Oracle 10g repo, I had to redeploy IdM and connect. Didn't understand if the drivers were corrupted.

 

 

And we do have a deployment of an another application on the WAS, which uses the WAS data source to connect to the same 10g Oracle instance. WAS 6.1.0.9 and JRE 1.5

 

 

For info, Sun guys tell us that setting the waveset.home property via the jvm (in the style -Dwaveset.home=D:\fred) should fix the idm 7.1, WAS 6.0 compatitibility problem we saw here. Haven't tried it yet though. I love computers.

Procedure for setting waveset.home from the WAS console:
1) Expand Servers
2) Click Application Servers
3) Click the name of the server you are running the application on.
4) Expand Java and Process Management
5) Click Process Definition
6) Click Java Virtual Machine
7) Click Custom Properties
8) Click New
Name = waveset.home
Value = <war directory> ( like C:\Program Files\.......\IDM71.war)

 

 

Hi,

We have recently upgraded from S nIdM 6.0 on WAS server, after upgrade server is failing to start, with excpetion pointing to varaibles.xml.
exception is:
Program exiting with error: com.ibm.ws.exception.WsRuntimeException:
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Package
with uri 'http://www.omg.org/XMI' not found.
(file:/export/home/idmadmin/WASHOME/profiles/AppSrv01/config/cells/dev01-sim-001Node01Cell/variables.xml,
3, 22), resulting from:
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Package
with uri 'http://www.omg.org/XMI' not found.
(file:/export/home/idmadmin/WASHOME/profiles/AppSrv01/config/cells/dev01-sim-001Node01Cell/variables.xml,
3, 22)
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file:
Any ideas on resolving this.

Thanks,