Pages: 1

#1 2019-08-20 16:25:31

drdec
Member
Registered: 2019-08-20

Installing on WebLogic and Oracle database

Hello,

I am trying to get ReportServer running on WebLogic 12c using an Oracle 12c database.  I am following the manual instructions from https://reportserver.net/en/guides/conf … tallation/.

I have configured the WEB-INF/classes/persistence.properties file as below:

hibernate.dialect=net.datenwerke.rs.utils.hibernate.Oracle12cDialect
hibernate.connection.driver_class=oracle.jdbc.driver.OracleDriver
hibernate.connection.url=jdbc:oracle:thin:@dbsrv01:1521:reports
hibernate.connection.username=reports
hibernate.connection.password=***********
hibernate.default_schema=reports

I placed the ojdbc7_g.jar file in the WEB-INF/lib/ directory.

I get a ClassNotFoundException, from what I can tell it seems that the values in the persistence.properties are not being used, for example, I see this in the log:

INFO: HHH010002: C3P0 using driver:  at URL:
Aug 20, 2019 12:10:14 PM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH000046: Connection properties: {user=, password=****, autocommit=false}

Any thoughts?

Rest of the log below:

<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.ResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.ApplicationAdapter because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.server.impl.application.DeferredResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.ClassNamesResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.DefaultResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,468 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.PackagesResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,484 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.servlet.WebAppResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,484 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.ClasspathResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,484 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192510> <Cannot add Jersey servlet for application class com.sun.jersey.api.core.ScanningResourceConfig because ApplicationPath annotation is not set on it.>
<Aug 20, 2019, 12:09:19,828 PM EDT> <Warning> <JAXRSIntegration> <BEA-2192511> <The list of resource packages: net.datenwerke.rs.saiku.server.rest.resources;org.codehaus.jackson.jaxrs>
Aug 20, 2019 12:10:14 PM org.hibernate.ejb.HibernatePersistence logDeprecation
WARN: HHH015016: Encountered a deprecated javax.persistence.spi.PersistenceProvider [org.hibernate.ejb.HibernatePersistence]; use [org.hibernate.jpa.HibernatePersistenceProvider] instead.
<Aug 20, 2019, 12:10:14,85 PM EDT> <Warning> <org.hibernate.ejb.HibernatePersistence> <BEA-000000> <HHH015016: Encountered a deprecated javax.persistence.spi.PersistenceProvider [org.hibernate.ejb.HibernatePersistence]; use [org.hibernate.jpa.HibernatePersistenceProvider] instead.>
Aug 20, 2019 12:10:14 PM org.hibernate.jpa.internal.util.LogHelper logPersistenceUnitInformation
INFO: HHH000204: Processing PersistenceUnitInfo [
        name: reportServerPU
        ...]
Aug 20, 2019 12:10:14 PM org.hibernate.Version logVersion
INFO: HHH000412: Hibernate Core {5.0.3.Final}
Aug 20, 2019 12:10:14 PM org.hibernate.cfg.Environment <clinit>
INFO: HHH000206: hibernate.properties not found
Aug 20, 2019 12:10:14 PM org.hibernate.cfg.Environment buildBytecodeProvider
INFO: HHH000021: Bytecode provider name : javassist
Aug 20, 2019 12:10:14 PM org.hibernate.annotations.common.reflection.java.JavaReflectionManager <clinit>
INFO: HCANN000001: Hibernate Commons Annotations {5.0.0.Final}
Aug 20, 2019 12:10:14 PM org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl populate
WARN: HHH90000006: Attempted to specify unsupported NamingStrategy via setting [hibernate.ejb.naming_strategy]; NamingStrategy has been removed in favor of the split ImplicitNamingStrategy and PhysicalNamingStrategy; use [hibernate.implicit_naming_strategy] or [hibernate.physical_naming_strategy], respectively, instead.
<Aug 20, 2019, 12:10:14,264 PM EDT> <Warning> <org.hibernate.orm.deprecation> <BEA-000000> <HHH90000006: Attempted to specify unsupported NamingStrategy via setting [hibernate.ejb.naming_strategy]; NamingStrategy has been removed in favor of the split ImplicitNamingStrategy and PhysicalNamingStrategy; use [hibernate.implicit_naming_strategy] or [hibernate.physical_naming_strategy], respectively, instead.>
Aug 20, 2019 12:10:14 PM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH010002: C3P0 using driver:  at URL:
Aug 20, 2019 12:10:14 PM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH000046: Connection properties: {user=, password=****, autocommit=false}
Aug 20, 2019 12:10:14 PM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH000006: Autocommit mode: false
<Aug 20, 2019, 12:10:14,546 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "532684723194799" for task "4" on [partition-name: DOMAIN]. Error is: "weblogic.application.ModuleException: java.lang.ClassNotFoundException: "
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
        at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
        at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException:
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:226)
        at org.hibernate.c3p0.internal.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:128)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:94)
        Truncated. see log file for complete stacktrace
>
<Aug 20, 2019, 12:10:14,559 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "reportserver".>
<Aug 20, 2019, 12:10:14,560 PM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.ClassNotFoundException:
        at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
        at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException:
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:226)
        at org.hibernate.c3p0.internal.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:128)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:94)
        Truncated. see log file for complete stacktrace
>

Offline

#2 2019-08-21 07:27:00

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Installing on WebLogic and Oracle database

Hi drdec,

what version exactly do you have? Oracle 12c  is not enough, you should see something similar to "12c Standard Edition Release 12.2.0.1.0 ".
I ask because it depends if you have 12.1 or 12.2: https://www.oracle.com/database/technol … -jdbc.html it depends which driver you need: "What are the Oracle JDBC releases Vs JDK versions?" in the link.

You may try with the ojdbc8.jar driver.

Also check the information on Oracle here: https://reportserver.net/en/tutorials/upgrade-30/
"In order to use ReportServer 3.0.8 with Oracle, the following jars (or newer versions) are needed: ojdbc6.jar, orai18n.jar, xdb6.jar and xmlparserv2.jar. These are needed because of the new XML/JSON support. Please download and copy them to the WEB-INF/lib directory. Note: we recommend to use ojdbc7.jar or newer because of this jdbc driver incompatibility with null parameters in BIRT reports."

Regards,
Eduardo

Offline

#3 2019-08-21 12:50:15

drdec
Member
Registered: 2019-08-20

Re: Installing on WebLogic and Oracle database

Thanks, Eduardo.  I am on Oracle DB 12.1.0.2.0.  I tried with ojdbc8.jar anyway and got the same result.

I feel like I have a more fundamental issue than what driver to use - based on the logging below, I wonder if the values in my persistence.properties are even being used.  As you can see, there is no value for the driver or URL or user.

Aug 21, 2019 8:36:35 AM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH010002: C3P0 using driver:  at URL:
Aug 21, 2019 8:36:35 AM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure
INFO: HHH000046: Connection properties: {user=, password=****, autocommit=false}
Aug 21, 2019 8:36:35 AM org.hibernate.c3p0.internal.C3P0ConnectionProvider configure

Just to confirm that the driver is not the issue, I tried switching to the PostgreSQL driver and got the same results as above.

Offline

#4 2019-08-21 13:13:10

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Installing on WebLogic and Oracle database

Hi drdec,

you should have some output like this in your logs (look for the big reportserver ASCII logo):

 _____                       _    _____                            ______       _                       _          
 |  __ \                     | |  / ____|                          |  ____|     | |                     (_)         
 | |__) |___ _ __   ___  _ __| |_| (___   ___ _ ____   _____ _ __  | |__   _ __ | |_ ___ _ __ _ __  _ __ _ ___  ___ 
 |  _  // _ \ '_ \ / _ \| '__| __|\___ \ / _ \ '__\ \ / / _ \ '__| |  __| | '_ \| __/ _ \ '__| '_ \| '__| / __|/ _ \
 | | \ \  __/ |_) | (_) | |  | |_ ____) |  __/ |   \ V /  __/ |    | |____| | | | ||  __/ |  | |_) | |  | \__ \  __/
 |_|  \_\___| .__/ \___/|_|   \__|_____/ \___|_|    \_/ \___|_|    |______|_| |_|\__\___|_|  | .__/|_|  |_|___/\___|
            | |                                                                              | |                    
            |_|                                                                              |_|                    

Version: RS3.0.8-6009 2019-07-12-15-35-44
Code Version: 2019-07-12-15-35-44
Java Version: Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.91-b14 (1.8)
VM Args: -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:55866 -Xmx2g -Drs.configdir=/opt/reportserver -Dfile.encoding=UTF-8
rs.configdir: /opt/reportserver (OK)

### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://127.0.0.1:3309/bitnami_reportserver (OK)
hibernate.connection.username: bn_reportserver
hibernate.connection.password: **********
hibernate.default_schema: 

Connection Test: OK
Schema Version: RS3.0-13

there you can see if the values are being read:
### DB Config ###
hibernate.dialect: net.datenwerke.rs.utils.hibernate.MySQL5Dialect (OK)
hibernate.connection.driver_class: com.mysql.jdbc.Driver (OK)
hibernate.connection.url: jdbc:mysql://127.0.0.1:3309/bitnami_reportserver (OK)
hibernate.connection.username: bn_reportserver
hibernate.connection.password: **********
hibernate.default_schema:

Please check this.

Regards,
Eduardo

Offline

#5 2019-08-21 13:26:29

drdec
Member
Registered: 2019-08-20

Re: Installing on WebLogic and Oracle database

I do not see the ASCII logo at all.  Also, I noticed that the stacktrace does not seem to have any reportserver classes, only weblogic and hibernate classes.  Is this expected?  I wonder if WebLogic is trying to initialize hibernate itself.  Do you know if anyone has run ReportServer on WebLogic before?

<Aug 21, 2019, 8:48:12,127 AM EDT> <Error> <Console> <BEA-240003> <Administration Console encountered the following error: weblogic.application.ModuleException: java.lang.ClassNotFoundException:
        at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
        at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
        at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
        at weblogic.application.utils.StateMachineDriver.nextStateInParallel(StateMachineDriver.java:144)
        at weblogic.application.internal.flow.ModuleStateDriver.parallelPrepare(ModuleStateDriver.java:46)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:75)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:55)
        at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:727)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
        at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:239)
        at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:52)
        at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
        at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:65)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:229)
        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:103)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:241)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:794)
        at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1340)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:267)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:177)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:186)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:14)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:666)
        at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
        at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
        at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
        at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
        at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
Caused by: java.lang.ClassNotFoundException:
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:348)
        at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.classForName(ClassLoaderServiceImpl.java:226)
        at org.hibernate.c3p0.internal.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:128)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:94)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:217)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:189)
        at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.buildJdbcConnectionAccess(JdbcEnvironmentInitiator.java:145)
        at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:66)
        at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:88)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:234)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:208)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:189)
        at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:51)
        at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:94)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:217)
        at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:189)
        at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.handleTypes(MetadataBuildingProcess.java:352)
        at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:111)
        at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:770)
        at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:797)
        at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:135)
        at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:50)
        at weblogic.persistence.BasePersistenceUnitInfo.initializeEntityManagerFactory(BasePersistenceUnitInfo.java:614)
        at weblogic.persistence.BasePersistenceUnitInfo.init(BasePersistenceUnitInfo.java:202)
        at weblogic.persistence.BaseJPAIntegrationProvider.createPersistenceUnitInfo(BaseJPAIntegrationProvider.java:54)
        at weblogic.persistence.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:422)
        at weblogic.persistence.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:128)
        at weblogic.persistence.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:56)
        at weblogic.servlet.internal.WebAppInternalModuleExtension$PersistenceExtension.setupPersistenceUnitRegistry(WebAppInternalModuleExtension.java:197)
        at weblogic.servlet.internal.WebAppInternalModuleExtension$PersistenceExtension.access$300(WebAppInternalModuleExtension.java:118)
        at weblogic.servlet.internal.WebAppInternalModuleExtension.prePrepare(WebAppInternalModuleExtension.java:56)
        at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:293)
        at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:285)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
        at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:109)
>
<Aug 21, 2019, 8:48:12,163 AM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "reportserver".>

Offline

#6 2019-08-21 13:40:05

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Installing on WebLogic and Oracle database

Hi drdec,

please setup logging accordingly, as you should definitely see reportserver logs and these are very important.

https://reportserver.net/en/tutorials/i … -practice/

Here you have a section on logging. Please take a look.

Regards,
Eduardo

Offline

#7 2019-08-21 14:10:42

drdec
Member
Registered: 2019-08-20

Re: Installing on WebLogic and Oracle database

Eduardo, with WebLogic I usually set up the logging in the application as opposed to at the AS level as described in the documentation you linked.  E.g. I use log4j2 and include a log4j2.xml configuration file in the WAR.

Which logging framework is being used by reportserver?  I see slf4j-*.jar and log4j-over-slf4j.jar in lib/ directory - so should I configure for log4j?

Offline

#8 2019-08-22 07:16:05

eduardo
Administrator
Registered: 2016-11-01
Website

Re: Installing on WebLogic and Oracle database

Hi drdec,

reportserver loads by default logback since it finds a logback configuration here: WEB-INF/classes/logback-rs.xml
It then loads the libraries found here:
/resources/optlib/jul-to-slf4j.jar
/resources/optlib/logback-classic.jar
/resources/optlib/logback-core.jar

so you should configure logback logging. Also take a look at the file logback-rs.xml for some details on this configuration.

I would recommend to install first the bitnami installer, where everything is configured already, so you have a reference installation where you see the logs, output, etc. Then, you can compare the different files and configurations with your manual configuration. The bitnami installer can be installed very quickly and easily: just click on "next" "next" etc. smile

Regards,
Eduardo

Offline

#9 2019-08-22 12:56:06

drdec
Member
Registered: 2019-08-20

Re: Installing on WebLogic and Oracle database

Thanks again Eduardo.

TL;TD - On WebLogic 12c I needed to edit the persistence.xml AND the persistence.properties in order to get the war to deploy successfully.

I tried editing the WEB-INF/classes/logback-rs.xml to add a file appender but that did not work.  I also tried naming it WEB-INF/classes/logback.xml but that also did not work.  However I do not feel this is an issue to focus on currently.

I noticed the WEB-INF/classes/META-INF/persistence.xml file and tried configuring the database information there.  I was successful in getting the application to deploy with the PostgreSQL driver.  I also saw the ReportServer logo in the console output, so it is getting further than before.  Of course, I didn't actually set up a PostgreSQL login for this so I get an expected authentication error.

So next I changed back to the Oracle driver (ojdbc7_g.jar, since that is recommended for my database and comes packaged with WebLogic) and I am waiting to see the results.... it looks like it is successful.  I am getting a stacktrace in the logs but it seems unrelated to the database.  I will investigate that and probably start a new thread if need be.

Offline

Pages: 1

Board footer

Powered by FluxBB