Hitachi Vantara Pentaho Community Forums
Results 1 to 10 of 10

Thread: How to make pat point at a different port?

  1. #1
    Join Date
    Apr 2007
    Posts
    2,009

    Default How to make pat point at a different port?

    Hi,

    I just downloaded pat and ran it up, and it says it tries to access http://localhost:8080

    The 3.5 platform runs on localhost:18080, where do i change this?

    I tried going to connect, xmla, and putting in the url as so:

    http://localhost:18080/pentaho/Xmla

    And put in the admin password, and it still said Connection could not be established.

    Is this right? where have i gone wrong?

    Thanks,
    Dan

  2. #2
    pstoellberger Guest

    Default

    PAT 0.4 comes with some demonstration modes (STANDALONE, OLAPTABLE, ONECUBE, BUSINESSUSER etc.) these demonstration modes will try to access standard pentaho xmla at localhost:8080/pentaho/Xmla

    however, these demo modes are just for demonstration purposes how different permission in the GUI can look like and what kind of MODE pat supports for integration into other apps

    if you want to make them work you're gonna need to compile PAT yourself and change DemoSetup.java (cc.setUrl("http://localhost:8080/pentaho/Xmla"); ) to the correct url

    you can still connect in the normal mode (no demo mode) to your xmla source
    so you would add a new connection with the credentials you described:
    http://localhost:18080/pentaho/Xmla / joe / password .. this will still work.. just the demo mode of different permissions won't

    if you want to compile PAT yourself, check out http://code.google.com/p/pentahoanal...rtedDevelopers

    PAT 0.4 includes some "demo" features like the connection list stuff / different permissions in the GUI .. this was just for demonstrating the way we're heading down.

    PAT 0.5 will have a complete rewritten GUI, and saving connections in the persistance layer will actually work (so whenever you start the application - probably in different browsers etc - you'll have the same connections available)

    you can get the bleeding edge copy from hudson: http://ci.pentaho.com/job/Pentaho_Analysis_Tool/org.pentaho$pat/
    it is not quite finished yet, so its buggy / not complete... but it gives a rough idea what PAT 0.5 will look like

    -paul

  3. #3
    Join Date
    Apr 2007
    Posts
    2,009

    Default

    ah ha, i was using admin/password which is for the console, not the platform, joe/password which didnt work either.

    but then i realised it was because sampledata db wasnt running, now it is!

    I'd quite like to nosy around and play with the tool, but i'm time constrained as everyone else is, so building from source may cost me a bit too much time!

    I'll let you know of any findings!

    many thanks!
    Dan

  4. #4
    pstoellberger Guest

    Default

    well then just 1) change biserver 3.5's port to 8080 - then demo mode will work again 2) new xmla connection should work now

    and as i said, the bleeding edge version might be worth a look as well: http://ci.pentaho.com/job/Pentaho_Analysis_Tool/org.pentaho$pat/lastSuccessfulBuild/artifact/org.pentaho/pat/0.5.0-SNAPSHOT/pat-0.5.0-SNAPSHOT.war


    in any case, we're appreciating any kind of feedback :-)

  5. #5
    Join Date
    Apr 2007
    Posts
    2,009

    Default

    Ok, i've got 0.4 working fine.

    I loaded 0.5 too, and it connected fine to 3.5, but when i try to browse a cube it says error getting cube list, and i see this in the log:

    ERROR - A RPC call resulted in the following exception :
    java.lang.UnsupportedClassVersionError: Bad version number in .class file

    Is this possibly something to do with the version of java that the biserver 3.5 runs under?

    Weird!
    Dan

  6. #6
    pstoellberger Guest

    Default

    yeah. 3.5 runs with JRE 1.5 but PAT from hudson was compiled with 1.6

    easiest way would be to switch the biservers JRE to 1.6 (if you just dropped the WAR into the biserver tomcat) or deploy PAT on a different tomcat that uses JRE 1.6

    i just talked to tom, we might consider providing PAT for java 1.5 builds again

  7. #7
    Join Date
    Apr 2007
    Posts
    2,009

    Default

    ok i'll do that, thanks. Dont worry about a java 1.5 build for me. I'm surprised bi server ships with 1.5, it's deprecated now by sun, so why isnt it shipped with java 6?

  8. #8
    Join Date
    Apr 2007
    Posts
    2,009

    Default

    Ok, got 0.5 working, but i can't get very far. I guess it's very much in progress as you say!

    in case im missing something, i'm using quadrant actuals, i've dragged some measures in, but i see no way of running the query!

  9. #9
    pstoellberger Guest

    Default

    yes, thats the current state.

    whats new so far:
    - actually saving connections in the hibernate persistance layer
    - new ui layout
    - new cube browser (that popup that shows connections/cubes)
    - new dimension selection
    - a fancy spinning wheel that indicates PAT is currently working (not important and in the wrong place, but i like it )

    next steps we're currently working on:
    - once you've moved the dimension to the right axis (rows, cols, filter) you can click on it and make the selection with a dimension browser (see attached screenshot of the mockup)
    - show canvas that is synchronized with the dimension selection drag n drop on the left. so you can decide how to select the dimensions. its just a different way of selecting the dimension. (see other attached screenshot of the mockup)
    - fix some things in the new table (column headers etc.)

    our orientation guideline about PAT 0.5 is the mockup done by jake cornelius, not everything will be included in 0.5 but we're getting there - accessible in our googlegroup: http://pentahoanalysistool-dev.googl...toryboards.ppt
    Attached Images Attached Images   

  10. #10
    Join Date
    Mar 2010
    Posts
    9

    Default

    Hi,
    does PAT 0.8 biserver plugin require any specific configurations for usage in non-default Pentaho port? I don't have any problems in the basic 8080 port, but another environment with https://<servername>:8443/pentaho provides errors in establishing the "Automatic Pentaho XMLA" connection. I have modified the XMLA connection properties through PAT Manage Connections to point to right address. Should I do some other configuration?

    Best regards,
    Sami Helin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2017 Pentaho Corporation. All Rights Reserved.