[Logo] SpagoWorld Forums
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing  
[Groups] Back to home page  [Moderation Log] Moderation Log   [Register] Register /  [Login] Login 
Messages posted by: zsoltputnoky.spw
Forum Index » Profile for zsoltputnoky.spw » Messages posted by zsoltputnoky.spw
Author Message
Hi,

I guess that this is happening because the document is already deployed on the server. When you re-deploy, it is overwriting the document definition only, not the settings.

Try to locate the document on the server and delete it from there - there might be a better solution, but I haven't find it yet. then you should be able to do a clean deploy of the new document.

Zsolt
Hi there,

When you deployed the document, I assume you selected a 'folder' where it should go. Please log in as BIADMIN and check what are the permissions on that folder. You can go to see the Document Browser application, that should show you the folders created. From there select the one into which you deployed your document, click on it to see its content, then try to launch the document.

Also check what permissions you set on that folder related to the different users.

Zsolt
Hello Forum,

I try to set up JNDI data connection, but being a total beginner in this subject, I need your expert opinion.

Here is what I do:

Open server.xml and add the following lines under the <GlobalNamingResources>:

<Resource
name="[resource name]"
auth="Container"
type="javax.sql.DataSource"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://[host]\[instance]:[port];databaseName=[database name]"
username="[user name]"
password="[assigned password]"
maxActive="20"
maxIdle="10"
maxWait="-1"
/>


Once it is done, I open the contect.xml under the %CATALINA_HOME%\webapps\[engine]\META-INF -> where the [engine] is all the different SpagoBI engines installed, and add the following line:

<ResourceLink global="[resource name]" name="jdbc/spagobi" type="javax.sql.DataSource"/> where the [resource name] is the name I created when modified the server.xml

At completion, I restart Tomcat and SpagoBI to declare the datasource as JNDI:

java:comp/env/jdbc/[resource name]

Can you please let me know whether it is okay or I am missing some steps?

Your help is appreciated,

Zsolt
Dont worry, I got help from the Forum, so I give back as much as I can.

Zsolt
aashish.jain16.spw wrote: Thanks A lot Zsolt for helping me.

I got your point now i have 1 more doubt.

As you told in All in one server we can connect with our own database with help of -> datasource - from Resources -> Data Source. Here you can add the connection to your own database.
So what is Use for this ....
I mean If we can't create reports charts etc in all in one then what we will do after connecting with Our own DB.

Thanks,
Ashish Jain


Hi there,

The All-in-One means: you have a Tomcat server, a SpagoBI MetaDB and all engines packaged into one file. This also means that you dont have to install Tomcat and configure, your MetaDB is up and running and you have all the engines installed. It is a fully working system. I did all my report using this version, then once all my tests were done, I created a custom installation - my own Tomcat, SpagoBI Meta is running in MySQL and deployed only the engines I wanted to use.

Here is what you do: install SpagoBI - this is a server actually, then install SpagoBI Studio which is used to design the reports, once the reports are designed you can upload them to the server where you can specify the access rights, and the organization, declare the different users, etc. The server itself allows you to do kinda basic reports - as far as I know - not an expert on this - but if you want something performant, use the Studio.

Zsolt
Hi Ashish,

The SpagoBI All-in-One gives you the server and all the SpagoBI Engines in a Tomcat bundle. This works properly and you can check all the functions of SpagoBI with the help of the samples. You can also create a new datasource - from Resources -> Data Source. Here you can add the connection to your own database.

To develop reports - which then are deployed in the server - you can use Birt or Jasper -> each has its own report design tool. But, the best is to use the SpagoBI Studio to create them. In the Studio you can declare your server, data sources, etc, design the queries, business models, and report layouts. You can also test them before you deploy it.

Once you are okay with all that, you can do your own SpagoBI implementation by removing the sample database and not used engines from Tomcat. It is a bit complex, but can be done

Zsolt
Hi Ashis,

Well that is a big subject. What you can do 1st is to have a look on the Wiki : http://wiki.spagobi.org/xwiki/bin/view/Main/ where you can find some information. What you need for sure is to install SpagoBI Studio, this is an Eclipse based tool to develop reports. There you can connect to MS SQL database and use either BIRT or Jasper to develop the reports.

I advise you to check out these two software to have an idea what to do with them.

I am not an expert myself, fighting to make it work :) properly, but try to help as much as possible.

Let me know what info you need,

Zsolt
Hi There,

I had similar issue earlier, have a look on this post:

http://www.spagoworld.org/jforum/posts/list/2045.page

I had to copy the SQLJDBC4.JAR into another folder as well. You will find it in the post mentioned.

Hope it helps,

Zsolt
Hi Eric,

I try to set up SpagoBI to run from our Ubuntu 12.04 server. Well, not much luck till now....I will try to follow your action list.
Are you actually aware of a good documentation about how to set up SpagoBI on Linux? I managed to make it work - properly - on my win7 machine..

Thanks alot,

Zsolt
Thanks to the help of SpagoBI, the solution is to copy the SQLJDBC4.JAR file into the:

%CATALINA_HOME%\webapps\SpagoBIBirtReportEngine\WEB-INF\platform\plugins\org.eclipse.birt.report.data.oda.jdbc_2.6.1.v20100909\drivers

folder. Restart Tomcat and it works.

Cheers,

Zsolt
Hi Alberto,

Thanks for the reply, I will try to make the 1st example work. So far I am using JDBC connection - however I have a problem with it, see post: http://www.spagoworld.org/jforum/posts/list/2045.page

I have done the following mod in the SpagoBI contect.xml file:

<Context docBase="SpagoBIProject" path="/SpagoBI" privileged="true" reloadable="true" source="org.eclipse.jst.j2ee.server:SpagoBIProject">
<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>
<ResourceLink global="jdbc/spagobi" name="jdbc/spagobi" type="javax.sql.DataSource"/>
<ResourceLink global="jdbc/pmdb" name="jdbc/pmdb" type="javax.sql.DataSource"/>
<!-- <ResourceLink global="jdbc/foodmart_hsql" name="jdbc/foodmart_hsql" type="javax.sql.DataSource"/> -->
<ResourceLink global="spagobi_resource_path" name="spagobi_resource_path" type="java.lang.String"/>
<ResourceLink global="spagobi_sso_class" name="spagobi_sso_class" type="java.lang.String"/>
<ResourceLink global="spagobi_host_url" name="spagobi_host_url" type="java.lang.String"/>
<!--ResourceLink global="spagobi_domain" name="spagobi_domain" type="java.lang.String"/-->
<ResourceLink global="wm/SpagoWorkManager" name="wm/SpagoWorkManager" type="jcommonj.work.WorkManager"/>
</Context>

When I try to create the data source in SpagoBI, connecting via JNDI to PMDB, I get the following message:

it.eng.spagobi.tools.datasource.service.TestConnectionAction.service: JNDI error
javax.naming.NameNotFoundException: Le Nom pmdb n'est pas liÚ Ó ce Contexte
at org.apache.naming.NamingContext.lookup(NamingContext.java:770)
at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
at org.apache.naming.NamingContext.lookup(NamingContext.java:140)
at org.apache.naming.NamingContext.lookup(NamingContext.java:781)
at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
at org.apache.naming.SelectorContext.lookup(SelectorContext.java:152)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at it.eng.spagobi.tools.datasource.service.TestConnectionAction.service(TestConnectionAction.java:76)
at it.eng.spago.dispatching.action.ActionCoordinator.invokeServiceBusiness(ActionCoordinator.java:209)
at it.eng.spago.dispatching.action.ActionCoordinator.service(ActionCoordinator.java:15
at it.eng.spago.dispatching.httpchannel.AdapterHTTP.service(AdapterHTTP.java:41
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at it.eng.spagobi.commons.filters.ProfileFilter.doFilter(ProfileFilter.java:109)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at it.eng.spagobi.commons.filters.SpagoBICoreCheckSessionFilter.doFilter(SpagoBICoreCheckSessionFilter.java:82)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:879)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:600)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1703)
at java.lang.Thread.run(Thread.java:662)

Which basically says that PMDB is not specified in the context.


Thanks alot,

Zsolt
Hello Forum,

Strange issue: I have the SQLJDBC4.JAR placed in the %CATALINA_HOME%\LIB folder. When I launch a report, simple one, I get the following error message on the consol:

22 janv. 2013 11:17:03 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadDriverExtensions
INFO: Found JDBC driverinfo extension: driverClass=org.apache.derby.jdbc.EmbeddedDriver, connectionFactory=null
22 janv. 2013 11:17:03 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadDriverExtensions
INFO: Found JDBC driverinfo extension: driverClass=org.eclipse.birt.report.data.oda.sampledb.Driver, connectionFactory=org.eclipse.birt.report.data.oda.sampledb.SampleDBJDBCConnectionFactory
22 janv. 2013 11:17:03 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadExtraDriver
GRAVE: DriverClassLoader failed to load class: com.microsoft.sqlserver.jdbc.SQLServerDriver
java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver


The report is displayed though.

I tried all what I can and proposed by Spago's developers (big thanks to them) but no luck. Have you ever noticed something like this?

Zsolt
Does not work:

I got the following error: The SQL JDBC driver is under catalina_home\lib

21 janv. 2013 15:14:19 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadExtraDriver
GRAVE: DriverClassLoader failed to load class: com.microsoft.sqlserver.jdbc.SQLServerDriver
java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
at org.eclipse.birt.core.framework.URLClassLoader.findClass1(URLClassLoader.java:185)
at org.eclipse.birt.core.framework.URLClassLoader$1.run(URLClassLoader.java:154)
at org.eclipse.birt.core.framework.URLClassLoader$1.run(URLClassLoader.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.birt.core.framework.URLClassLoader.findClass(URLClassLoader.java:149)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.loadExtraDriver(JDBCDriverManager.java:919)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.findDriver(JDBCDriverManager.java:73
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.registerDriver(JDBCDriverManager.java:879)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.loadAndRegisterDriver(JDBCDriverManager.java:862)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doConnect(JDBCDriverManager.java:246)
at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getConnection(JDBCDriverManager.java:212)
at org.eclipse.birt.report.data.oda.jdbc.Connection.connectByUrl(Connection.java:235)
at org.eclipse.birt.report.data.oda.jdbc.Connection.open(Connection.java:160)
at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaConnection.open(OdaConnection.java:250)
at org.eclipse.birt.data.engine.odaconsumer.ConnectionManager.openConnection(ConnectionManager.java:165)
at org.eclipse.birt.data.engine.executor.DataSource.newConnection(DataSource.java:222)
at org.eclipse.birt.data.engine.executor.DataSource.open(DataSource.java:210)
at org.eclipse.birt.data.engine.impl.DataSourceRuntime.openOdiDataSource(DataSourceRuntime.java:20
at org.eclipse.birt.data.engine.impl.QueryExecutor.openDataSource(QueryExecutor.java:406)
at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:316)
at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:44
at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.produceQueryResults(PreparedDataSourceQuery.java:190)
at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:17
at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery.execute(PreparedOdaDSQuery.java:145)
at org.eclipse.birt.report.data.adapter.impl.DataRequestSessionImpl.execute(DataRequestSessionImpl.java:617)
at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:152)
at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:265)
at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1876)
at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:80)
at org.eclipse.birt.report.engine.executor.DataItemExecutor.execute(DataItemExecutor.java:75)
at org.eclipse.birt.report.engine.internal.executor.dup.SuppressDuplicateItemExecutor.execute(SuppressDuplicateItemExecutor.java:43)
at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:46)
at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:34)
at org.eclipse.birt.report.engine.layout.html.HTMLBlockStackingLM.layoutNodes(HTMLBlockStackingLM.java:65)
at org.eclipse.birt.report.engine.layout.html.HTMLPageLM.layout(HTMLPageLM.java:90)
at org.eclipse.birt.report.engine.layout.html.HTMLReportLayoutEngine.layout(HTMLReportLayoutEngine.java:99)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:180)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:77)
at it.eng.spagobi.engines.birt.BirtReportServlet.runReport(BirtReportServlet.java:690)
at it.eng.spagobi.engines.birt.BirtReportServlet.service(BirtReportServlet.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at it.eng.spagobi.utilities.filters.SpagoBIAccessFilter.doFilter(SpagoBIAccessFilter.java:193)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:879)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:600)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1703)
at java.lang.Thread.run(Thread.java:662)
21 janv. 2013 15:14:19 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadExtraDriver
GRAVE: refreshUrlsWhenFail: true
21 janv. 2013 15:14:19 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadExtraDriver
GRAVE: driverClassPath: null
21 janv. 2013 15:14:19 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadExtraDriver
GRAVE: Registered URLs:

Then this one:

21 janv. 2013 15:14:21 org.eclipse.birt.report.engine.api.impl.RunAndRenderTask doRun
GRAVE: There is insufficient memory to execute this report.
Thanks alot Monica, just trying now.

Zsolt
Hello Forum,

Started to receive the error message below:



I tried to find the cause but not much luck, any ideas?

Zsolt
 
Forum Index » Profile for zsoltputnoky.spw » Messages posted by zsoltputnoky.spw
Go to:   
Powered by JForum 2.1.9 © JForum Team