Re: How-To: How-To: Using a custom Java class in UCCX 5.x (SOAP - Page 3

Anthony Holloway · ‎07-08-2008

Update: Due to the loss of dropbox, the links to dropbox offline project are no longer active. Please use this awesome document as your new reference:

https://supportforums.cisco.com/document/97736/uccx-8x-really-simple-soap-client-no-custom-jar

~~Update: Due to a server failure, the links to http://www.avholloway.com/ are no longer active. Please download the offline project.~~

This tutorial can be viewed in its entirety on my web site:

http://www.avholloway.com/vtools/ipcc/custom-java/soap/

The first thing we need to do is find out what version of Java is our server running, this way we know which version of Java to compile in.

This document outlines the JRE (Java Runtime Environment) version compatibility with all versions of CRS:

"Cisco Customer Response Solutions (CRS) Software and Hardware Compatibility Guide" - June 16, 2008

http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf

According to that document, my version of CRS, v5.0(1) SR2, uses JRE 1.5.0. So I will go to Sun's site and download the JDK (Java Development Kit) for that version.

Alternatively, you could determine the Java version right on the CRS server itself. Though, there could be multiple JRE's installed, and the CRS Engine uses only the one listed in the above document.

Sun's page for previous JDK versions:

http://java.sun.com/javase/downloads/previous.jsp

I would typically install the JDK and JRE for 1.5.0 on my personal computer and not on the server. This way I can do all of my Java testing offline, making sure it all works, before even uploading it to the server. I did one additional, and optional, thing to make developing easier. I added the bin directory to my path variable so I can execute the necessary Java commands from any directory. This is outlined in the installation instructions, which can be found on the JDK download page.

So now we have our development environment setup. Yep, all we needed was the JDK, and the JRE, the only other tool we'll use it already on every system; a text editor. I will use TextEdit on my Mac for this example, but you could easily use Notepad on Windows, or nano on Linux.

I will not get into the details of writing Java apps/classes, so for the purpose of this tutorial I will offer my simple SOAP class to you.

Disclaimer: I am not a Java programmer. In fact, this is my very first program in Java, and I learned just enough for this task.

Browseable link: http://www.avholloway.com/vtools/ipcc/custom-java/soap/SimpleSOAP.java.txt

Download link: http://www.avholloway.com/vtools/ipcc/custom-java/soap/SimpleSOAP.java

Now, we need to compile our source code into byte code so the JRE can execute it. Compiling the .java file will result in a new file of the same name, but with the .class extension on it.

http://www.avholloway.com/vtools/ipcc/custom-java/soap/compiling-SimpleSOAP.png - Command Prompt>javac SimpleSOAP.java

Now we need to test this new class to see if it works before we add the complexity of the CRS environment.

Let's create another Java file, and this one will utilize our newly created class.

Browseable link: http://www.avholloway.com/vtools/ipcc/custom-java/soap/RunMyCode.java.txt

Download link: http://www.avholloway.com/vtools/ipcc/custom-java/soap/RunMyCode.java

Now we compile that source code so it can also be ran.

http://www.avholloway.com/vtools/ipcc/custom-java/soap/compiling-RunMyCode.png - Command Prompt>javac RunMyCode.java

Next we pass the RunMyCode class to the JRE like so (Note the absence of the .class or .java file extension):

http://www.avholloway.com/vtools/ipcc/custom-java/soap/running-RunMyCode.png - Command Prompt>java RunMyCode

Your output should look something similar to this:

Screen shot: http://www.avholloway.com/vtools/ipcc/custom-java/soap/running-RunMycode.png

Browseable link: http://www.avholloway.com/vtools/ipcc/custom-java/soap/soap-response.xml

OK, so if everything is working up to this point, it's safe to assume that our CRS server will be able to utilize our class as well.

Anthony Holloway · ‎03-28-2011

I agree that it's the xml namespace messing it up, hence the end of my post talking about it not working.

Take a look at this example:

veer.pratap · ‎02-23-2011

Thanks anthony, i was use the custom calss , but unable to load the script in the application on UCCX it is giving error " An error occurred while loading the script SCRIPT{test.aef}, please check the logs for more details."

I am having UCCX 5.0 with premium licence.

Regards,

Veer Pratap

amanbasra · ‎03-23-2011

I am having a similar problem. I developed and tested my script using custom Java classes in Cisco Unified CCX Editor, and was able to run them fine and get results using Debug mode. Then I uploaded the script using UCCX App Admin > Script Management, that was also fine. But when I attempt to associate that IVR script to a UCCX Application using Application Management, I am getting the following error:

"Failed to load script file; com.cisco.script.ScriptIOException:Failed to load script: C:\Documents and Settings\Administration\My Documents\Downloads\Hyundai-v1.6-Aman.aef; nested exception is: com.cisco.io.IOException: bad version number in .class file; nested exception is: java.lang.UnsupportedClassVersionError: Bad version number in .class file"

We are using Cisco Unified CCX and Cisco Unified IP IVR,Release 7.0(1)SR5 Solution Set. As per Cisco documentation, the supported Java versions for this UCCX version are: Custom Classes/SDK> Sun JRE 1.5.0_011; Sun JRE 1.5.0_014; Sun JRE 1.6.0_12. I confirmed that my Java classes are compiled for backward compatibility with Sun JRE 1.5. (It is only possible to compile for a x.y version, not the minor update version denoted by the underscore.)

I also checked the JRE version on the UCCX server:

C:\>java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)

Will greatly appreciate advice!

Anthony Holloway · ‎03-23-2011

I have no idea. Can you try compiling with the exact version cisco recommends?

marks · ‎03-25-2011

hi guys

i thought i would add my two pence wirth in here.

if you are getting errors when loading you need to reboot the server just restarting the node manager is not enough.

i am having a strange issue though.

I have wrote a custom class and i can reference it in the expression editor no issues. i can attach the script to an application with no issues.

but when trying to debug under reactive script the application never fires into the debug window.

anyone got any ideas on this one?

not sure if it is because i am using public classes or not. Oh and this works perfect from my dev machine when compliled in same version as the UCCX

matrix say to use.

any thoughts

thanks

Mark

Stephen Earl · ‎03-25-2011

Hi Mark,

What specific version of UCCX are you using?

Steve E.

marks · ‎03-25-2011

i have tried this on UCCX 8.0.2 and UCCX 8.5.1

UCCX 8.0.2 just will not fire the script at all

UCCX 8.5.1 will allow the script to start in debug mode but then complains about my constructor which is fine on the test java test machine (Not uccx)

Mark

Stephen Earl · ‎03-25-2011

Hi Mark,

Any SUs on 8.0.2?

I'm betting your running into an issue related to the following bug ID: CSCti50428

There's an overly restrictive java security policy in place on 8.0.2 and 8.5.1.

If you ssh into the admin shell on those servers and issue the following command you can tail stdout.log which will display the specific security exception(s):

file tail activelog uccx/log/MIVR/stdout.log

Steve E.

Anthony Holloway · ‎03-25-2011

+5 points for an excellent post on real-time monitoring of MIVR logs. Thanks!

marks · ‎03-25-2011

Yes SU3 on 8.02

where is there details on this?

is there a way to switch off / work around?

:S

Mark

Stephen Earl · ‎03-25-2011

It's in the bug database under the bug id I posted previously CSCti50428.

If you're on SU3 then you already have an "opened up" security policy. I actually worked on a deployment yesterday evening of 8.0.2 SU3 and applying SU3 fixed our security policy issues. For 8.5.1, currently, you'll have to work with TAC to get the updated security policy applied.

It may be something else alltogether. If you can tail that stdout.log and post any exceptions we may be able to diagnose further.

Steve E.

marks · ‎04-21-2011

Hi Guys

I had to upgrade to V 8.5.1 now getting no errors at all in the stdout log or the MIVR. just get ringing and then system error message.

reactive debug does not work either just times out.

Any more ideas?

do i have enough debuging on?

Mark

Chad Stachowicz · ‎08-25-2011

All,

I thought I would toss in my 2 cents. I think UCCX 8 still looks pretty untested compared to 7.x. I wrote a pretty big salesforce.com integration last year.. About 7 megs after axis2 code generation and 40 megs with all required libs. UCCX 8.0(2)SU3 wants nothing to do with it. I can load the classes in the editor, write and validate the script. Upload the script and thats as far as I get. When trying to create an application with the script it bomb out with the MADM logs posted below... I can't even launch the script for debugging in the editor either if the custom classes are in use... I have posted the script below to humor you all.. MADM logs as well

I have a TAC case open and as soon as I get it sent to dev (today I hope) I will report back.

Chad

39277: Aug 25 00:50:48.070 MDT %MADM-ADM_CFG-7-UNK:AppUtil.getConfigVarFromWf() - scriptName=SCRIPT[Test.aef]

39278: Aug 25 00:50:48.071 MDT %MADM-DB_MGR-7-UNK:getConnection request for :: CRS Repository Datastore

39279: Aug 25 00:50:48.105 MDT %MADM-SCRIPT_MGR-3-UNABLE_LOAD_SCRIPT:Unable to load script: Script=/Test.aef,Exception=java.io.StreamCorruptedException: unexpected block data

39280: Aug 25 00:50:48.105 MDT %MADM-SCRIPT_MGR-3-EXCEPTION:java.io.StreamCorruptedException: unexpected block data

39281: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1343)

39282: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)

39283: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)

39284: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

39285: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

39286: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

39287: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.steps.core.StepAssign.readObjectCurrentVersion(StepAssign.java:255)

39288: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.steps.core.StepAssign.readObject(StepAssign.java:225)

39289: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

39290: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

39291: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39292: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39293: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)

39294: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)

39295: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

39296: Aug 25 00:50:48.106 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

39297: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

39298: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFBeanStep.readObjectCurrentVersion(WFBeanStep.java:537)

39299: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFBeanStep.readObject(WFBeanStep.java:401)

39300: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

39301: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

39302: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39303: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39304: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)

39305: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)

39306: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

39307: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

39308: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

39309: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.util.DoublyLinkedList.readObject(DoublyLinkedList.java:333)

39310: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

39311: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

39312: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39313: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39314: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)

39315: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)

39316: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

39317: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

39318: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

39319: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFWorkflow.readObjectCurrentVersion(WFWorkflow.java:1115)

39320: Aug 25 00:50:48.107 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFWorkflow.readObject(WFWorkflow.java:860)

39321: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

39322: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

39323: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39324: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39325: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)

39326: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)

39327: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)

39328: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)

39329: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)

39330: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFWorkflow.load(WFWorkflow.java:267)

39331: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.script.impl.ScriptManagerImpl.loadInternal(ScriptManagerImpl.java:297)

39332: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.script.impl.ScriptManagerImpl.load(ScriptManagerImpl.java:2143)

39333: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.script.Script.load(Script.java:370)

39334: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.script.Script.load(Script.java:389)

39335: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.appadmin.util.AppUtil.getConfigVarFromWf(AppUtil.java:656)

39336: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.jsp.protected_.Cisco_005fScript_005fApplication_jsp._jspService(Cisco_005fScript_005fApplication_jsp.java:366)

39337: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

39338: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

39339: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)

39340: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39341: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39342: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)

39343: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39344: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)

39345: Aug 25 00:50:48.108 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)

39346: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)

39347: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)

39348: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:56)

39349: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)

39350: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39351: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)

39352: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)

39353: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)

39354: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)

39355: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:65)

39356: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:80)

39357: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39358: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:294)

39359: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.appadmin.ui.AppAdminServlet.forwardToJSP(AppAdminServlet.java:495)

39360: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.appadmin.ui.AppAdminServlet.processService(AppAdminServlet.java:370)

39361: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.appadmin.ui.AppAdminServlet.doPost(AppAdminServlet.java:213)

39362: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)

39363: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

39364: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)

39365: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39366: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39367: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)

39368: Aug 25 00:50:48.109 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39369: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)

39370: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)

39371: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)

39372: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:283)

39373: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:56)

39374: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)

39375: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39376: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)

39377: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at com.cisco.appadmin.util.XssFilter.doFilter(XssFilter.java:167)

39378: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source)

39379: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

39380: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.reflect.Method.invoke(Method.java:597)

39381: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:269)

39382: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39383: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)

39384: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:301)

39385: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:243)

39386: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)

39387: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:56)

39388: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:189)

39389: Aug 25 00:50:48.110 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.security.AccessController.doPrivileged(Native Method)

39390: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)

39391: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

39392: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

39393: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)

39394: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

39395: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

39396: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)

39397: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:421)

39398: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

39399: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)

39400: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)

39401: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

39402: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)

39403: Aug 25 00:50:48.111 MDT %MADM-SCRIPT_MGR-3-EXCEPTION: at java.lang.Thread.run(Thread.java:619)

39404: Aug 25 00:50:48.111 MDT %MADM-ADM_CFG-7-UNK:AppUtil.getConfigVarFromWf() - ScriptException com.cisco.script.ScriptIOException: Failed to load script: /Test.aef; nested exception is:

java.io.StreamCorruptedException: unexpected block data

39405: Aug 25 00:50:48.111 MDT %MADM-ADM_CFG-7-UNK:AppUtil.getConfigVarFromWf() - returning null

39406: Aug 25 00:50:48.111 MDT %MADM-ADM_CFG-7-UNK:ScriptApp.jsp - script not foundSCRIPT[Test.aef]

amanbasra · ‎03-30-2011

Thanks Mark and Anthony,

1. The following error was resolved by restarting UCCX Application Administration service. This was the error that was occurring when attempting to associate that IVR script to a UCCX Application using Application Management.

" An error occurred while loading the script SCRIPT{xxx.aef}, please check the logs for more details."

2. The other error was easier to resolve, as it just requires that when working on an IVR script with Java classes you should always run UCCX Editor from the UCCX server (as mentioned in Anthony's how-to doc.)

"Failed to load script file; com.cisco.script.ScriptIOException:Failed to load script: C:\Documents and Settings\Administration\My Documents\Downloads\Hyundai-v1.6-Aman.aef; nested exception is: com.cisco.io.IOException: bad version number in .class file; nested exception is: java.lang.UnsupportedClassVersionError: Bad version number in .class file"

andywallace · ‎07-20-2011

Hmm i am trying to get this working but seem to be stuck at the first hurdle. I have installed the correct SDK/JRE on my pc. I compiled the code. (so far so good) however when i run it Java RunMyCode it brings back the HTML for the actual ASMX and not the XML. Where have i gone wrong?

Any help would be much appreciated.

I found the problem. the link for the webservice has now changed.

change your URL to (note the f)

http://wsf.cdyne.com/WeatherWS/Weather.asmx";

Message was edited by: Andy Wallace

How-To: Using a custom Java class in UCCX 5.x (SOAP Example)