As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
I am able to get output for EXL2K with .mht template file.
But with .xltm(macro enabled template file) for EXL07 output, I am getting below error message.
Error: (FOC1522) ntjprerr: org/apache/xml/serialize/OutputFormat. CPJAVA: Error in (FOC1522) processing EXECUTE command for Class ibi.jsexcel.JscomExcelUnzip
Thanks, RamThis message has been edited. Last edited by: Ram Prasad E,
CPJAVA: Error in processing INIT command for Class ibi.jsexcel.JscomExcelZip/ Ensure JSCOM3(JVM) service is running; check -Djava.class.path in edaprint.log
WebFOCUS 7.7.03/8.0.08 Dev Studio 7.7.03/8.0.08 App Studio 8.0.08 Windows 7 ALL Outputs
Posts: 402 | Location: Upland, IN | Registered: June 08, 2012
I am kind of facing a similar one as well. CPJAVA: Error in processing INIT command for Class ibi.jsexcel.JscomExcelUnzip/ Ensure JSCOM3(JVM) service is running; check -Djava.class.path in edaprint.log (FOC3317) Error processing template file.
Resetting the Java home path and restart of Tomcat & Reporting Server solved the issue.This message has been edited. Last edited by: tomatosauce,