I downloaded and installed the the Mondrian 3.4.1 stable community release with the embedded derby database instance. I have many of the examples up and running on a local tomcat instance, but I cannot get the XMLA examples to work, and I am unable to communicate with the XMLA endpoint using xmla4js (http://code.google.com/p/xmla4js/ the discover-schema-rowsets example allows you to specify a url to hit, which for my local instance is localhost:8080/mondrian/xmla).
I have edited the 'datasources.xml' file as found here: http://pentahodave.mywebcommunity.org/#Apache7
The xmlaTest.jsp produces the same error as the one found at the bottom of the page, but the .class link no longer works, and I am not configured to build the source locally yet.
So my question is two-fold: Is there a way to get the xmlaTest.jsp to work without a local build and what else can I do to get xmla4js to talk to Mondrian?
The JPivot project is very old and not up to date with the current Mondrian codeline. Actually, we will be removing JPivot from our distribution as of Mondrian 4.0. In the meanwhile, if you wish to test your XMLA service, I suggest you use Warehouse Explorer.
Related
I have SonarQube for Bamboo plugged in and working fine with MSBuild. I also have SonarQube or bit bucket server, which, as far as I can tell, is configured correctly, but pull request analysis is not working. I have a repository in bit bucket configured to allow Sonar Qube analysis and have min. severity set to INFO. But when I click the pull request, a box on the right says:
"Sonar data unavailable. Was not able to fetch data for Sonar project "[project name]:[branch name]". Either the build is not finished yet, your pull request has not been analyzed or a non-existing Sonar project is referenced. You can configure the referenced Sonar project in the repository settings."
The referenced project is configured right in the repo settings, and I have branch analysis for this project working just fine on sonar qube server from the bamboo plugin. The pull request analysis just won't jive while everything else is working. Anyone seen this issue? Any ideas as to why?
Bit bucket server v4.13.0
Sonar for bit bucket server 1.13.1-bbs4
Could you please create a bug report at https://support.mibexsoftware.com ? We can then analyze the issue in detail. It would also help if you could send us the debug logs of the plug-in. I can give you more detailed instructions after we have your bug report.
Thanks,
Michael from Mibex Software
Firstly, there are related posts:
GlassFish Server update center installation times out
Java EE 7 updatetool installation fails
I got my Java EE 7 SDK (Update 3) from here: http://www.oracle.com/technetwork/java/javaee/downloads/index.html
I have tried each of the solutions in the above posts and here: https://blogs.oracle.com/dipol/troubleshooting-glassfish-update-center
Including:
In the cmd prompt running set PKG_CLIENT_CONNECT_TIMEOUT=300 and set PKG_CLIENT_READ_TIMEOUT=300 before updatetool in C:\glassfish4\bin\updatetool.bat (c:\glassfish4 in my install directory - all settings were default, including install update tool...).
Set above mentioned timeout to much larger values - doesn't appear to make a difference at all, the process basically bombs immediately.
Running C:\glassfish4\bin\updatetool.bat many times.
Triple checking that I didn't somehow configure a proxy server in my sleep.
Use the update tool via the Glassfish admin console at http://localhost:4848 (seems to show no available update or add-ons, which seems odd..)
I get the following screenshot when I run C:\glassfish4\bin\updatetool.bat
I have no idea why the error would be proxy related, unless it happened to be something on their end. Interestingly, If I go directly to the URL mentioned (via Chrome) I get the following page:
What could possibly be going wrong here?
The updatetool was a commercial feature of Oracle GlassFish. Any update functionality relied on Oracle providing a site where updates could be hosted. Since Oracle GlassFish is no longer supported, this site no longer exists so the updatetool won't work any more.
Rather than downloading GlassFish from Oracle, you should download it from the official open source site, hosted on GitHub. Alternatively, if you really do need support, you could try Payara Server which is open source, and derived from GlassFish, but has support available (disclaimer: I work for Payara)
I created a simple project using ATG 10.2 .I want to know how to deploy it in weblogic. Please provide detailed procedure with screenshots,if possible.
To provide a 'detailed' procedure is beyond the scope of what StackOverflow is trying to provide. That said, if you have an understanding of the Weblogic Management Console you should be able to follow these steps to setup your initial deployment:
Create a Server
1.1 Specify a server name (eg. commerce) and the port number this server will run on (eg. 8180). Select it as a 'Stand-alone server'.
1.2 Once created go to Configuration > Server Start for the newly created server and modify the 'Arguments' block and include the following setings (assuming you are running windows, for Unix update your own paths)
-Datg.dynamo.data-dir=c:\ATG-Data -Datg.dynamo.server.name=commerce -d64 -XX:ParallelGCThreads=8 -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Xms1152m -Xmx2048m -XX:NewSize=128m -XX:MaxNewSize=256m -XX:PermSize=128m -XX:MaxPermSize=256m
1.3 Save your Server
Create DataSources
2.1 In the Console click on 'Services > Data Sources'
2.2 Create 'New' datasources for each of your connections. As a minimum you will need connections for ATGSwitchingDS_A, ATGSwitchingDS_B (Assuming you are doing switching datasources) and ATGProductionDS. These names should match your JNDI names in your property files. Remember to specify the 'commerce' server as the target for each of the datasources.
Create Deployment
3.1 Assuming you've already built your EAR (eg. ATGProduction.ear) and it is available in c:\deployments you need to create a deployment in Weblogic. You need to create the deployment in the console and specify the target as 'commerce'. Once done you need to also 'start serving requests' on the deployment.
Start Server
You should now be able to see your server running on port 8180 with the log files being written to c:\ATG-Data\servers\commerce\logs.
If after this things aren't running, post specific questions about your issues and someone here might be able to help you.
i'am trying to integrate hybris 4.7.9 with endeca. I have installed the following endeca components. 1)MDEX engine 2)Platform services 3)Endeca workbench 4)CAS.
I have deployed a sample application on endeca side using "D:\Endeca\ToolsAndFrameworks\11.0.0\deployment_template\bin\deploy.bat"
In Hyend2 in admincockpit of hybris
I have made EAC/CAS connection with my appication and made a export job.
Problem is i am not able to run that job, it reports me following error:
http://localhost:8500/MyAppen_en_data/?wsdl returned response code 404
at com.endeca.itl.service.ServiceLocator.getService(ServiceLocator.java:150)
I don't know Hybris, but since the error is related to Endeca, let me try to give some pointers.
CAS: Check that CAS is up and running
App Name: You might have specified app-name-with-locale (MyAppen) somewhere where you need to specify only app-name (MyApp). [The Endeca app name without the locale is called as "Base Application Name". Go back and check all your configurations in Hybris and Endeca].
You may also refer to this blog (Although it is for ATG framework, it should give idea for Hybris as well).
I have a webapp that I'm trying to use Mondrian within. And I'm getting the following exception when I try to open a connection:
Caused by: mondrian.olap.MondrianException: Mondrian Error:Internal error: Virtual file is not readable: /WEB-INF/olap/mycube.xml
I have tested this cube using a plain J2SE program from the command line, and it works fine. However, when I tried to execute the same cube in my web application I get the error above. My connect string is the following:
jdbc:mondrian:Jdbc=jdbc:mysql://${server.db.host}/HRWarehouse?user=${server.db.username}&password=${server.db.password};Catalog=/WEB-INF/olap/mycube.xml;
This is very similar to what I've found in the Mondrian web application. However, somehow that application has installed the ServletContext in the VFS, but there is exactly zero documentation out there that I can find through google about any sort of special configuration for mondrian in a web application.
I have worked around the issue by setting the path to the schema to be absolute reference instead of relative to webapp context. While this has allowed me to continue testing it is not a suitable solution to the problem. I'm looking for a answer on how to that fix the exception that allows a webapp context relative URL.
I think you need to specify the work file in the Catalog,
`jdbc:mondrian:Jdbc=jdbc:mysql://${server.db.host}/HRWarehouse?user=${server.db.username}&password=${server.db.password};Catalog=file:/path/to/schema.xml;`
I cant recall if it was absolute path or not, try both again.
I would also double check the connection string just to make sure it's written properly. Also, here is a link that might end up helpful if you don't have it already.
Update
Try to add jndi:/ at the beggining of your path:
jndi:/localhost/path/to/file.xml