Up to sometimes back i could perform compartment search on HAPI DSTU2 server, but now i am not able to do so. The following is the request format i was using:
http://fhirtest.uhn.ca/baseDstu2/Patient/1548313/Condition
Also please let me know about other servers which support Compartment search.
Unfortunately I don't believe that has ever worked on the HAPI server. HAPI has support for compartments in its server modules, but the test server does not have that part turned on yet.
We are hoping to work on this soon though..
Related
My team is working on making our REST API more 'hypermedia' by replacing compound documents with links to related resources. We'd obviously like to use HTTP/2 Server Push to make sure it's as fast as possible. However, because of our hosting provider, we are not able to run HTTP/2.
It seems like the second best option after Server Push would be to have the client prefetch related resources via Preload.
Does anyone know if OkHttp natively supports the Link rel=preload header?
It does not. But you should be able to enqueue these yourself by inspecting the headers.
Can anyone advice if is it possible Sitecore would work with Oracle Commerce/ATG 11.3 and Endeca?
There is no reason why it can't be integrated, it depends how deeply you want to integrate it. For example SiteCore exposes a RESTful API that allows you to get to individual content items.
Since you mention Endeca as well, I assume you want to be able to index the content too? For that you will probably have to develop your own CAS connector, potentially hooking in to the SiteCore search functionality.
There may be other APIs to hook into as well but since your question is whether it is possible. The answer is still 'Yes'.
As for whether it is the right solution, that is a different question. What does SiteCore give you that the BCC doesn't? Can you migrate from SiteCore to the BCC? Does SiteCore expose other APIs that will allow them to be 'read-only' stores in an ATG application (BCC or Storefront)? Many options exist.
We faced with the problem that we need to do such thing as dynamic routing and canary releases. So, for example, we deploy microservice microservice-1. Then, when someone finished a big feature we want to deploy it as a microservice microservice-1.1.
Question
Is it possible to dynamically reroute requests using information, for example, from Headers, and route to the microservice version microservice-1.1 instead on microservice-1?
For example, someone needs this feature and he will modify/add specific Header and for all requests, he will use new microservice-1.1. And if that Header is missing then the current microservice-1 version should be used.
For service discovery, I am using Eureka. Right now I am looking at linkerd but there is no support for Eureka and I am working on it right now. Of course, if it is possible to do it using Zuul that would be great. Please advise where to look at.
Not really sure about Netflix Zuul, but we liked the approach presented by Istio (backed by Google, etc) which works really well with Containers (Kubernetes) and you get the support for canary releases https://istio.io/blog/2017/0.1-canary/
I deployed integration edition of document server on windows machine. I want to make many changes on document server as per my suitability. So I wanted to know the meaning of each and every parameter in default.json to achieve my goal. Is there any proper documentation for default.json so that I could thoroughly know the meaning of each parameter and accordingly use those parameter.
No, there is no such doc. You can try to figure it out by looking at changes for https://github.com/ONLYOFFICE/server/blame/master/Common/config/default.json
Unfortunately today we do not have complete documentation for default.json. We already have plans for full refactoring of Document Server configuration
and writing detailed documentation for default.json. We understand the importance of it but any time frames for it could not be specified.
Thank you for the interest in our product.
I have a Elasticsearch running on my server by default it runs on port 9200 and link is public means any one can insert, update, delete anything form anywhere. How do I make it secure like phpMyadmin which can be only accessed with the help of my code and not directly from browser or postman.
Elasticsearch does not perform authentication or authorization, leaving that as an exercise for the developer. Two popular ways I have seen are
Setup your own proxy (Nginx/HAProxy) fronting elasticsearch - this way you exercise full control. You can also use the Elasticsearch-jetty plugin to have jetty level auth
Shield - If budget permits use Shield which is a paid offering from Elasticsearch - https://www.elastic.co/products/shield
Even with these in place, depending on who you are exposing this to - you may want to disable certain things like dynamic scripting, throttles for DoS etc.
You can use the Elasticsearch basic authentication plugin - https://github.com/Asquera/elasticsearch-http-basic
The README there gives a good idea on how to set it up.
If you are using Kibana3 as a frontend to elasticsearch, you can secure it using https://github.com/fangli/kibana-authentication-proxy
I have enabled a relatively simple Nginx proxy that sits between my Elasticsearch and Kibana to configure authorized access to my dashboards and charts.
Look at my post here: https://udaysagars.wordpress.com/2016/04/04/how-i-configured-authorized-access-to-kibana-dashboards/
Also, you can view my application that uses this method here: http://udaysagar2177.github.io/ec2/twitter-analytics.html