KB-1531 Invoking a process model as a webservice fails when using Weblogic application server: 'Error loading WSDL. There was something wrong with the WSDL you are trying to import'

Parmida Borhani — Mon, 23 Jul 2018 03:22:01 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:22:01 AM

Symptoms

Users are unable to invoke an Appian process model exposed as a web service when using Weblogic as the application server. This same web service works as expected when used with JBoss as the application server.

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue applies to all versions of Appian using Weblogic application server.

Last Reviewed: March 2018

Tags: weblogic, process models, application server, integration, web services

KB-1531 Invoking a process model as a webservice fails when using Weblogic application server: 'Error loading WSDL. There was something wrong with the WSDL you are trying to import'

Parmida Borhani — Thu, 29 Mar 2018 07:34:25 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 3/29/2018 7:34:25 AM

Symptoms

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue applies to all versions of Appian using Weblogic application server.

Last Reviewed: March 2018

Tags: weblogic, process models, application server, web services

KB-1531 Invoking a process model as a webservice fails when using Weblogic application server: 'Error loading WSDL. There was something wrong with the WSDL you are trying to import'

Parmida Borhani — Thu, 29 Mar 2018 03:34:25 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 3/29/2018 3:34:25 AM

Symptoms

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue applies to all versions of Appian using Weblogic application server.

Last Reviewed: March 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server: 'Error loading WSDL. There was something wrong with the WSDL you are trying to import'

Parmida Borhani — Thu, 29 Mar 2018 03:31:27 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 3/29/2018 3:31:27 AM

Symptoms

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: March 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server

Parmida Borhani — Thu, 29 Mar 2018 03:30:30 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 3/29/2018 3:30:30 AM

Symptoms

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: March 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server

Tejas Kargutkar — Wed, 28 Feb 2018 13:40:59 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 2/28/2018 1:40:59 PM

Symptoms

Users are unable to invoke an Appian process model exposed as a web service when using Weblogic as the application server.

This same web service works as expected when used with JBoss as the application server.

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives you an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: February 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server

Tejas Kargutkar — Wed, 28 Feb 2018 13:40:46 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 2/28/2018 1:40:46 PM

Symptoms

Users are unable to invoke an Appian process model exposed as a web service when using Weblogic as the application server.

This same web service works as expected when used with JBoss as the application server.

The web service endpoint can be accessed directly in a web browser, but invoking it via SOAP UI gives you an error of the following type:

Cause

The JVM arguments for WebLogic have been configured via the WebLogic Administration Console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the WebLogic Administration Console.

Action

Review the Configure JVM Settings documentation page to fix this issue by adding the JVM arguments via the start up script.

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: February 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server

Tejas Kargutkar — Tue, 27 Feb 2018 21:28:47 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 2/27/2018 9:28:47 PM

Symptoms

Unable to invoke an Appian process model exposed as a web service when using Weblogic as the application server.

This same web service works as expected when used with Jboss as the application server.

The web service endpoint can be accessed directly in a web browser, but, invoking it via SOAP Ui or Postman ends up with an error.

Cause

The JVM arguments for Weblogic have been configured via the Weblogic Administration console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the Weblogic Administration console.

Action

The following Appian documentation explains on how to get around this by adding the JVM arguments via the startup script instead for Weblogic:

https://docs.appian.com/suite/help/latest/Configuring_WebLogic.html#configure-jvm-settings

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: February 2018

Tags: weblogic, process models, application server, web services

Invoking a process model as a webservice fails when using Weblogic application server

Tejas Kargutkar — Tue, 27 Feb 2018 16:29:12 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 2/27/2018 4:29:12 PM

Symptoms

Unable to invoke an Appian process model exposed as a web service when using Weblogic as the application server.

This same web service works as expected when used with Jboss as the application server.

The web service endpoint can be accessed directly in a web browser, but, invoking it via SOAP Ui or Postman ends up with an error.

Cause

The JVM arguments for Weblogic have been configured via the Weblogic Administration console.

Weblogic has been observed to not pick up changes in the JVM arguments done through the Weblogic Administration console.

Action

The following Appian documentation explains on how to get around this by adding the JVM arguments via the startup script instead for Weblogic:

https://docs.appian.com/suite/help/latest/Configuring_WebLogic.html#configure-jvm-settings

Affected Versions

This issue affects all versions of Appian using Weblogic application server.

Last Reviewed: February 2018

Tags: weblogic, process models, application server, web services