Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Allan Bowe
    @allanbowe
    It's not actually a SAS (or adaptor) issue, as neither of those things can affect same origin policy
    your choices are : 1) launch browser with web security disabled, 2) adjust web server settings to allow cross domain requests from your machine, or 3) serve your web app direct from the SAS Web Server
    cpagrawal
    @cpagrawal
    okay Now I am getting warning
    Allan Bowe
    @allanbowe
    ok :-) should work now hopefully!
    cpagrawal
    @cpagrawal
    let's see
    no I am getting the same error
    :)
    I think I am going to be ram down today, My client will kick me out
    Allan Bowe
    @allanbowe
    I don't understand your last sentence (said, sheepily)
    can you confirm that you can in fact access a stored process on that domain without using the adaptor
    does that give anything?
    cpagrawal
    @cpagrawal
    Yes
    It is working properly
    { "usermessage" : "blank", "logmessage" : "H54S Exception - Input object datain was not found", "requestingUser" : "", "requestingPerson" : "", "executingPid" : 20788, "sasDatetime" : 1794158767.5 , "status" : "inputTableNotFound"}
    Allan Bowe
    @allanbowe
    have you tried adding the port to the hostUrl parameter?
    {hostUrl: 'http://vm00002596:8080/'}
    cpagrawal
    @cpagrawal
    yes, I tried. But I am getting the same error.
    can you help me with this : -
    cors can solve this problem ?
    Allan Bowe
    @allanbowe
    cors IS the problem
    can you try serving from the web server instead?
    do you have access?
    cpagrawal
    @cpagrawal
    you mean localhost ?
    I do not have chrome there .
    Allan Bowe
    @allanbowe
    you don't need a browser there, just to save the .html and .js files into the root
    cpagrawal
    @cpagrawal
    XMLHttpRequest cannot load http://vm00002596:8080/SASLogon/Logon.do. Redirect from 'http://vm00002596:8080/SASLogon/Logon.do' to 'http://vm00002596.solon.prd/SASLogon/login' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://vm00002596' is therefore not allowed access.
    Allan Bowe
    @allanbowe
    use the fully quaified domain in your hostUrl parameter
    {hostUrl: 'http://vm00002596.solon.prd:8080/'}
    cpagrawal
    @cpagrawal
    getting same error
    I need to leave. I will continue the work at home on my vmware machine.
    Thank You for support.
    Allan Bowe
    @allanbowe
    Allan Bowe
    @allanbowe
    Hey guys - are there any plans to host a CDN for the h54s .js library? Perhaps with copy-paste SRI ?
    Nikola Markovic
    @boemska-nik
    @rawfocus one would assume you'd have heard of rawgit :smile:
    if you haven't, check it out
    Nikola Markovic
    @boemska-nik
    I found where we know @cpagrawal from!!!
    good to meet you in person CP
    cpagrawal
    @cpagrawal
    It was nice meeting. 😀
    pmc129
    @pmc129
    Hello, I am trying to build a Web App on a customer's SAS Infrastructure. I copied h54s.js, h54s.min.js and your example index.html file to same directory on the SAS Web Server. Via the Chrome console I tried execute a stored process and got the error message "Unable to parse response json". I defined the adapter as var adapter=new h54s({hostUrl: 'https://stuff.company.net/',maxXhrRetries: 0, debug: false}); and executed the call function as adapter.call('/Metadata_Directory/Program',null,function(err, res) {
    if(err) {
    //Houston we have a problem
    console.log(err);
    } else {
    //res is an object returned from the server
    console.log(res);
    }
    });
    It appears the stored Process does not get executed. Do have any idea, what the problem could be? Sadly I have no experience in web developing.
    pmc129
    @pmc129
    the full Error Message is
    "h54sError: Unable to parse response json
    at new h54sError (SERVER/h54s.js:12:11)
    at Object.success (SERVER/h54s.js:575:24)
    at XMLHttpRequest.request.onreadystatechange (SERVER/h54s.js:391:27)"
    Nikola Markovic
    @boemska-nik
    hey @pmc129 - noooo idea why we didn't get alerted on this ^^
    next time drop us a line or raise an issue
    the adapter is really designed to be used by developers with some front-end / javascript experience, but you can possibly make some progress if you're keen to do it yourself
    you'll need to have a look at the network tab in the chrome console to see what's going on and what's being returned by your SAS server when the function fires
    marouanegana
    @marouanegana

    Hello , EveryBody I need a general Advice ! So here is the situation :

    We have already a Java web application developped on SAS portal. ( Architecture : SAS - Oracle - Java ( with private frameworks for front end )
    A new version will be developed and we have to change the architecture so that front end developers can Use Angluar and drop Java .
    My question is , do you think that this migration can be tottaly handled with h54S as using SAS as a Backend for the App ?
    Second , the app features will be kind of complicated since we're dealing about Acturial Analysis , so is it worth it if you talk about performances and lot of users ?

    Finallly wich solution will be more efficient :
    1- SAS + H54s ==> Angular
    2-SAS <==> Java back end ==> Angular front

    Thanks for any Help and have a nice Day !

    Allan Bowe
    @allanbowe
    @marouanegana - great choice! We use Angular + H54s + SAS for all of our apps, it's efficient / scalable / secure. As your developers are probably aware, the Angular framework is built to handle complex applications (even actuarial ones!) with it's component based architecture and type safety (typescript), not to mention '00s of other good reasons.