How to verify what version of solr is being used by Retrieve and Rank service on Bluemix in order to refer exact version of solr api and documentation of Solr.
Related
So recently I started studying MongoDB Atlas. So just wanted to know how I can integrate that cloud database to any cloud integration tool such as MULESOFT. Do I have to create an API from MongoDB Stitch and then integrate it or am I missing something?
Help would be much appreciated.
Specifically for Mule Runtime (MuleSoft is the company name, not a product) you can use the MongoDB connector to connect an application to a MongoDB database. For Atlas compatibility I have seen it is recommended to set the authenticationDB configuration.
MongoClientURI uri = new MongoClientURI(
"mongodb+srv://<username>:<password>cluster0-kjxf3.mongodb.net/test?retryWrites=true&w=majority");
MongoClient mongoClient = new MongoClient(uri);
Returns Response message:Exception: java.lang.IllegalArgumentException: uri needs to start with mongodb://. Above URL example comes from MongoDB Atlas manual, deleting +srv causes:
java.net.UnknownHostException: mongodb.net: Name or service not known
As per Driver Examples documentation section
To connect to an Atlas M0 (Free Tier) cluster, you must use Java version 8 or greater and use a Java driver version that supports MongoDB 3.4. For complete documentation on compatibility between the Java driver and MongoDB, see the MongoDB compatibility matrix.
So make sure to download MongoDB Java Driver version 3.4 or higher and drop it to JMeter Classpath. You will also need to remove all previous versions of the MongoDB Driver to avoid Jar Hell. JMeter restart will be required to pick up the new .jar and unload old ones (if any)
You may also find MongoDB Performance Testing with JMeter article useful.
I'm trying to figure out what version of MongoDB is used by CosmosDB?
Tried checking out azure cosmosdb portal for more information but there is no specific version mentioned on it.
From this link:
The Azure Cosmos DB's API for MongoDB is compatible with MongoDB
server version 3.2 by default. The supported operators and any
limitations or exceptions are listed below. Features or query
operators added in MongoDB version 3.4 are currently available as a
preview feature. Any client driver that understands these protocols
should be able to connect to Azure Cosmos DB's API for MongoDB.
In modern Azure Portal UI they display the version of your Cosmos DB in the Overview section:
I am planning to use orientdb in production using the jdbc drive so i need confirm some points
is jdbc driver can give all the orientdb Features like (transaction and links ...etc) or using the the java api is the best choice
I noticed that you have spring data implementation in the orientdb github is it ready to use in the production
At this link a discussion on the issue that you wrote.
in general, JDBC driver supports only a subset of OrientDB, only the part you can use with commands.
If you're a Java developer, I suggest you to use the Java Graph API: http://orientdb.com/docs/last/Graph-Database-Tinkerpop.html
I have clusted the WSO2 API Manager 1.8 and implemented deployment synchronization according to this guide which is given in the WSO2 documentaion. Everything happens to work find except one thing.
Let's assume that we have below 2 instances running API Manager.
192.168.X.123 - API Manager 1
192.168.X.124 - API Manager 2
The problem is once I create and publish an API on API Manager 1 it does appear on API Manager 2 in the publisher. But the particular API does not appear on the API Manager 2 Store.
Also note that I'm using a shared MySQL database for the API Manager cluster(API Manager 1 and 2). I checked the logs but does not contains any error.
How can I fix this?
Please look at WSO2 Clustering and Deployment Guide. Please check the docs on Clustering API Manager and SVN-based Deployment Synchronizer
If all configurations are correct, your API should be displayed in Store once you have "Published" the API. It might take some time (may be few minutes) to appear in Store due to indexing etc.
In our situation, we defined 2 different servers with extra CPU and
memory, on these servers we have installed the full WSO2 API Manager
and defined the cluster configuration. Everything provisioned via
Puppet.
Just a straightforward install, all data-source pointing to one schema
in an Oracle database.
And...it is working; Our Developers happy, Operations happy, Architect
department happy
From WSO2 API Manager Clustering configuration