I'm doing a demo in MF Studio 7.1, but I can not make the direct update work in the studio, I have test on at leat 3 workstations. Anyone knows why?
Please see the Direct Update tutorial, and specifically the following section: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/advanced-client-side-development/using-direct-update-to-quickly-update-your-application/#underTheHood
Because MobileFirst Platform Foundation Server 7.1 is session-independent, this affects Direct Update as well.
The setting of when to check for a Direct Update is now based on tokens; the check for an update will be made only once the token expires.
You can adjust it in the following ways:
Remove the wl_DirectUpdate realm from the used security test in authenticationConfig.xml and instead explicitly call the WL.Client.checkForDirectUpdate API to check for an update
Change the wl.realm.expiration.directUpdate value in the your-project\server\conf\worklight.properties file to a lower value.
Note for production environments: The lower the value, the more network traffic will incur. The value should be configured with care.
Related
I am facing a weird problem today, when running my MuleSoft application locally from my AnypointStudio and firing a request from postman, I am getting 403 error. When debugging I found out that the application is checking for flowVars._clientName, however it is missing. According to this documentation, actually yes flowVars._clientName is expected.
https://help.mulesoft.com/s/article/How-to-get-the-client-application-name-in-a-flow-based-on-the-client-id-and-client-secret.
So my application fails with 403 error. Seems that other environments are working perfectly fine.
And yes it is using Client Id enforcement.
Any clues?
Without more details it looks like the issue is inside the logic of your application. The KB article that you referenced is a how to in case you need to obtain the client name. It doesn't say that you have to use for authentication. You don't describe how the application does authentication/authorization. Is it in a flow? Or in a policy? If it is the standard Client ID enforcement policy, the expressions to evaluate client id and secret can be configured, but I don't think the default is not #[flowVars._clientName] nor #[flowVars._clientId].
Note that Exchange is basically a repository of APIs and other artifacts. It doesn't authenticate anything at execution time. Unless your application is trying to use it somehow, but I can't think of a reason for that.
The issue was resolved only by re-downloading Anypoint Studio and mule runtime. Very weird, it was happening only for one application, not for the others. Creating a new workspace did not help, deleting the application and re-cloning and installing did not help, even recloning in a new directory did not help. Only using a new Anypoint Studio and runtime installation resolved it (even with the old code base) ...
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)
Our ServiceNOW instance recently got upgraded from Eureka to Geneva.
MID Server status became down and the version does not match the Build number in the stats.
I was told that the MID Server will auto upgrade which didn't happened. I am using a proxy server to connect, when I tried communicating with the instance through the server it is working however I assume the service or application installed is not able to communicate with the instance.
I created a new service and it worked perfectly for 1 min however after that the status of it became down.
Then I tried changing the configurations of old services however no good.
Now the services are running fine however in the config file in the mid_sys_id section mid server details not getting populated and the status of the MID Server in the instance is always down.
Do I need to change any properties in the instance?
Since I use proxy server do I need to remove the comment line of the auto upgrade through proxy section or can I leave that blank?
What is the issue here? Why my MID Server is not getting upgraded? Kindly help me.. If possible an explanation with screen shot would be much appreciated.
If you're on Geneva, you should be able to simply go to your MIDServer listing, from inside your instance, click on a MIDServer, and find 'Upgrade MID' in the Related links section. That should start an upgrade for that MID Server. If it fails, there should be an entry in either the ServiceNow logs or the MID Server logs with more information why it failed.
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).
We have a web service returning an array of data from a backend system and the service is integrated using an Adapter procedure.
On one machine, when the data is returned, i notice that the JSON object name that hosted the data is called "array". As such, when i want to access the data, i use invocationResult.array . All is well.
But when my colleague gets my code and run on her machine, the JSON returned from the adapter have "text" instead as the object name for the data. With this, my code essentially is giving out error as "array" is then became unidentified.
Why is it that the object name is different on different set of machine?
UPDATE
My colleague machine runs version 6.1 Worklight Studio Plugin, while mine runs on 6.0. However another machine that runs with version 6.1 encountered no issue at all. Is this something to do with a Worklight settings?
Another info that i'm not sure will help or not, the problematic machine runs on Windows Server 2008 while others run on Windows 7 Professional
You're probably running a newer version of WL server/studio. WL adapters know how to process JSON responses. However in your case response is not JSON object, but an array. Older version of WL server treats it as plaintext, therefore you have a "text" property. Newer version of WL server knows how to handle arrays and interprets it as an array. The best approach here would be to use same lastest WL server/studio version on both machines. Alternatives might be manual conversion of array string to array object via JS APIs.
As it turns out, the problem lies in the adapter returnedContentType setting. The version on my colleague has a value 'plain' while the actual one should be 'json'
Many thanks to #Anton as it was his answer that pointed me to the correct direction.