Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
Expand all | Collapse all

NOT able to create CPE Profile due to soap connection

  • 1.  NOT able to create CPE Profile due to soap connection

    Posted Fri May 21, 2021 09:05 AM

    Dears,

    while creating CPE profile i am not able to connect WebSphere i already check WebSphere is up and running and also dmgr port also correct and location also connect still not able to connect to WebSphere please help to to fix this issue. i am getting below error in metadata/.log please check log below.

    ( !ENTRY com.ibm.ecm.configmgr.app.ce 4 0 2021-05-20 12:34:31.919

    !MESSAGE Connection error: The connection to the application server cannot be established. Ensure the application server is running and that the SOAP connector port and host name are correct.

    !STACK 0

    com.ibm.ecm.configmgr.engine.ConfigurationManagerException: Connection error: The connection to the application server cannot be established. Ensure the application server is running and that the SOAP connector port and host name are correct.

    at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethods(JMXInvoker.java:243)

    at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethod(JMXInvoker.java:142)

    at com.ibm.ecm.configmgr.engine.jmx.WebSphereJMXInvoker.connect(WebSphereJMXInvoker.java:86)

    at com.ibm.ecm.configmgr.app.ce.applicationserver.WebsphereApplicationServer$TestActivity.testWork(WebsphereApplicationServer.java:371)

    at com.ibm.ecm.configmgr.engine.profile.EnvironmentTestActivity.test(EnvironmentTestActivity.java:64)

    at com.ibm.ecm.configmgr.ui.wizards.NewProfileWizardPageGetProfileEnvironmentProps$7.widgetSelected(NewProfileWizardPageGetProfileEnvironmentProps.java:604)

    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)

    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)

    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)

    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.ProfileNewHandler.execute(ProfileNewHandler.java:67)

    at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)

    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.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829)

    at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815)

    at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805)

    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)

    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)

    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)

    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)

    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)

    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)

    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)

    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

    at com.ibm.ecm.configmgr.app.ce.rcp.Application.start(Application.java:86)

    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

    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:344)

    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:95)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

    at java.lang.reflect.Method.invoke(Method.java:620)

    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)

    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)

    at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

    Caused by: java.lang.Exception: The connection to the application server cannot be established. Ensure the application server is running and that the SOAP connector port and host name are correct.

    at com.ibm.ecm.configmgr.utils.websphere.WebSphereJMXUtil.connect(WebSphereJMXUtil.java:227)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)

    at java.lang.reflect.Method.invoke(Method.java:620)

    at com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethods(JMXInvoker.java:191)

    Regards

    Sadath



    #FileNet
    #Support
    #SupportMigration


  • 2.  RE: NOT able to create CPE Profile due to soap connection

    Posted Fri May 21, 2021 09:07 AM

    WebSphere Version : 8.5.5.12

    Content Platform Engine Server : 5.5.0

    WebSphere JDK : 1.7 and 1.8



    #FileNet
    #Support
    #SupportMigration