GVP 8 & WebLogic?

[Adam G]

I've been trawling for any info on GVP 8 utilizing WebLogic (version?) for deployments, but can't find any references... does anyone have any info on this?  Can GVP 8 utilize WebLogic - or does it have to be IIS/Tomact/Apache...? The standard compatibility documents contain no reference to this - either that, or I am missing the point!

Thanks!

[cavagnaro]

I would test by just creating a Java Project, export to WAR and then test the libraries working on WebLogic.
Should be a simple test

[Adam G]

Thanks cav - I was actually looking for a statement of compatibility from Genesys, as a reference.  I understand that, by design, it [i]should[/i] work... but I need documented proof from the vendor.

[cavagnaro]

Let me look at some docs I have. Will return to you in a few hours. If do, will send it to you directly

[cavagnaro]

A quick search on support site states that no, is not supported. Others already asked for it.

[Adam G]

Thanks for the confirmation cav!

[zafzef.mourad]

WebLogic and WebSphere are supported with GVP 8 ...so you can deploy your Composer, VXML and Java application....we used for our deployment in a big bank

Envoyé de mon Nexus 5 en utilisant Tapatalk

[cavagnaro]

? Any doc sustaining that?

[zafzef.mourad]

If u have a Genesys account so sign in and open this URL and see section "Application Server Requirements"

Envoyé de mon Nexus 5 en utilisant Tapatalk

[zafzef.mourad]

If not so here is the section:

Application Server Requirements

Genesys does not certify Composer with specific Web application server vendors and versions. This applies to developing both:

VXML applications and related resources that will be executed on the Genesys Voice platform andSCXML applications and related resources that will be executed on the Orchestration platform.

Java Composer Projects can be deployed to any Web application server that meets the following minimum pre-requisites:

Application server should be J2EE 5 compliant.Support for the JSP 2.1/Servlet 2.5 specification.

When considering a potential Web application server to use for a production deployment of Composer-generated applications, please refer to the vendor's documentation to ensure that the software meets these pre-requisites. In addition, you should run a few basic tests using a Composer sample application, to ensure that the application behaves as expected. For more details, please refer to the section Suggested Test Plan.

For developing SCXML applications and related resources that will be executed on the Orchestration Server platform, only specific Web application servers are supported. Please refer to the Orchestration Server 8.1 Deployment Guide for more information.

Note: For more detailed information on deploying Composer applications to an application server, see Deploying Composer Applications.

Envoyé de mon Nexus 5 en utilisant Tapatalk

[Adam G]

Thanks guys,

I also got a little more information on the subject which indicates that WebLogic can be used with VXML if the underlying data stream is standard HTTP/HTTPS but it has not necessarily been confirmed against any non-standard data stream.

Pretty much the same as noted in this thread...

[cavagnaro]

only thing I could find on all G support site:

[quote]
Connection Pooling for WebLogic Application Servers

When the application Server is WebLogic, there must be an extra configuration file in WEB-INF called weblogic.xml.  First, though, confirm that the following is present in web.xml in the exported .war file: <resource-ref>                <res-ref-name>jdbc/poolDS</res-ref-name>                <res-type>javax.sql.DataSource</res-type>                <res-auth>Container</res-auth> </resource-ref> res-ref-name should match the pool name in the connection.properties file, and it should be prefixed by jdbc/. weblogic.xml File The weblogic.xml can be added to the Composer Project in WEB-INF.  Afterwards, you will have to export the .war file from Composer again and redeploy.  The weblogic.xml should contain: <?xml version="1.0" encoding="UTF-8"?> <wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd&quot;>    <wls:resource-description>        <wls:res-ref-name>jdbc/poolDS</wls:res-ref-name>        <wls:jndi-name>poolDS</wls:jndi-name>    </wls:resource-description> </wls:weblogic-web-app> Note the following: The wls:res-ref-name should match res-ref-name in web.xml. wls:jndi-name should be the JNDI Name in the WebLogic configuration. 
[/quote]

This is from Composer docs