FileNet Configuration Manager setting issue

http://webcache.googleusercontent.com/search?q=cache:_PCYKHiUYDAJ:ecmplace.com/viewtopic.php%3Ff%3D102%26t%3D16307+&cd=3&hl=es-419&ct=clnk&gl=mx  FileNet Configuration Manager setting issue I am trying to configure FileNet 5 CE on WAS 7.0.0.13 on Windows 2008 R2 machine Websphere security is configured for Standalone LDAP server ( Active directory ). When I go to Application Server cell dropdown in the Profile section of FileNet Configuration Manager , I get the following error ( shown at the top ) - com.ibm.ecm.configmgr.engine.ConfigurationManagerException: An error occurred while retrieving information from server: When I manually enter the cell name in the Application Server cell dropdown box and click on Test Connection , I get the following error in the logs - com.ibm.ecm.configmgr.engine.ConfigurationManagerException: An error occurred while retrieving the cell name information. WebSphere:process=server1,type=ConfigService,* at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethods(JMXInvoker.java:218) at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethod(JMXInvoker.java:122) at com.ibm.ecm.configmgr.engine.jmx.WebSphereJMXInvoker.connect(WebSphereJMXInvoker.java:83) at com.ibm.ecm.configmgr.app.ce.applicationserver.WebsphereApplicationServer$TestActivity.testWork(WebsphereApplicationServer.java:338) at com.ibm.ecm.configmgr.engine.profile.EnvironmentTestActivity.test(EnvironmentTestActivity.java:64) at com.ibm.ecm.configmgr.ui.wizards.NewProfileWizardPageGetProfileEnvironmentProps$3.widgetSelected(NewProfileWizardPageGetProfileEnvironmentProps.java:445) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at com.ibm.ecm.configmgr.app.ce.handlers.EditAppServerPropsHandler.execute(EditAppServerPropsHandler.java:45) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:770) at org.eclipse.ui.menus.CommandContributionItem.access$10(CommandContributionItem.java:756) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:746) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.ibm.ecm.configmgr.app.ce.rcp.Application.start(Application.java:85) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) Caused by: javax.management.InstanceNotFoundException: WebSphere:process=server1,type=ConfigService,* at com.ibm.websphere.management.configservice.ConfigServiceProxy.<init>(ConfigServiceProxy.java:67) at com.ibm.ecm.configmgr.utils.websphere.WebSphereJMXUtil.getCells(WebSphereJMXUtil.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethods(JMXInvoker.java:178) ... 46 more Any idea on how to proceed or things to look out for ? Thanks, Amit
Thu Jun 16, 2011 7:32 am
amitu ECMPlace User Joined: Thu Jun 16, 2011 7:19 am Posts: 11	Re: FileNet Configuration Manager setting issue I was finally able to get past this error by reinstalling WAS 7.0.0.13 (ND). Currently, test connection works with dmgr SOAP port (8879) but it doesn't for the appserver port(same config service error). I am using the dmgr port for further deployment (not sure if it is correct). All my datasource tests are successful. When I try to deploy the application using the Configuration Manager, I get the following error: Starting to run Deploy Application Deploy Application ********************** Finished running Deploy Application An error occurred while running Deploy Application Running the task failed with the following message: The application deployment failed. WASX7209I: Connected to process "dmgr" on node WINADV95CellManager01 using SOAP connector; The type of process is: DeploymentManager Turn off RMI/IIOP SSL configure server transaction time out ADMA5016I: Installation of FileNetEngine started. ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=WINADV95Cell01,node=WINADV95CellManager01,server=server1 for module acce.war+WEB-INF/web.xml. ADMA5011I: The cleanup of the temp directory for application FileNetEngine is complete. ADMA5014E: The installation of application FileNetEngine failed. WASX7017E: Exception received while running file "C:\AMSAPPS\FileNetCE\tools\configure\tmp/deployapplication.tcl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7132E: Application install for C:\AMSAPPS\FileNetCE\tools\configure\profiles\AdvantageProfile\ear\Engine-ws.ear failed: see previous messages for details. Even though , I select the node as WINADV95Node01 ( in the graphical interface ) , I am not sure why it is taking it as WINADV95CellManager01. Any idea about this. Thanks, Amit Attachments: FileNet_CM_Screenshot.jpg [ 138.55 KiB | Viewed 1187 times ]  File comment: Cell Topology Cell_topology.jpg [ 51.9 KiB | Viewed 1187 times ]
Mon Jun 20, 2011 4:11 am
FunkMaster Moderator Joined: Fri Oct 08, 2004 9:47 am Posts: 2228 Location: United Kingdom	Re: FileNet Configuration Manager setting issue Before tackling the issue you describe, I noticed that your on WAS 7.0.0.0 - but the SW requires at a minimum WAS 7.0.0.9 Page 12: https://www-304.ibm.com/support/docview ... aid=7&wv=1 _________________ Kind Regards Robert Brauer ECMPlace - Site Administrator "The driving force behind a good implementation is a brilliant implementation team ... are you part of that team?"
Mon Jun 20, 2011 8:28 am
amitu ECMPlace User Joined: Thu Jun 16, 2011 7:19 am Posts: 11	Re: FileNet Configuration Manager setting issue Actually, we are using WAS 7.0.0.13 ( as described in my earlier post). I was able to get past the error. Steps followed were as follows - 1. Used the dmgr SOAP port in the application server properties. 2. For ND based WAS , it seems it needs cluster based environment. So, I created a cluster based environment and added server1 under it. 3. The Deployment type selected under deployment task was Cluster based and my deployment ran successfully. I was able to deploy the FileNet CE in server1 present under a cluster. Am in the process of configuring the Enterprise Manager. We are looking for uploading/downloading attachments in FileNet through webservices provided by FileNet from our application(Java based ). We also need to be able to search for the documents uploaded in FileNet. This is the only requirement . Do we need to install FileNet Process Engine. Are there any good links to refer to for using Java WebServices in FileNet. Thanks, Amit
Mon Jun 20, 2011 5:00 pm
amitu ECMPlace User Joined: Thu Jun 16, 2011 7:19 am Posts: 11	Re: FileNet Configuration Manager setting issue My bad. During my reinstall of WAS, I had missed out to install the FixPack and so , my latest WAS version was 7.0.0.0 Thanks for pointing it out. Regards, Amit
Mon Jun 20, 2011 5:21 pm
FunkMaster Moderator Joined: Fri Oct 08, 2004 9:47 am Posts: 2228 Location: United Kingdom	Re: FileNet Configuration Manager setting issue amitu wrote: Actually, we are using WAS 7.0.0.13 ( as described in my earlier post). We are looking for uploading/downloading attachments in FileNet through webservices provided by FileNet from our application(Java based ). We also need to be able to search for the documents uploaded in FileNet. This is the only requirement . Do we need to install FileNet Process Engine. Are there any good links to refer to for using Java WebServices in FileNet. Thanks, Amit If your not planning on doing any Process related activities, there is no need to install the Process Engine. https://www-304.ibm.com/support/docview ... SNVNV&wv=1 Go look there, under the heading FileNet Developer Samples ... some stuff there might be of use to you _________________ Kind Regards Robert Brauer ECMPlace - Site Administrator "The driving force behind a good implementation is a brilliant implementation team ... are you part of that team?"