I can give you some simple information, but it would also help if you would clarify in what contexts you actually need information from both Mashup Servers. It would help get a better answer than I think this general answer may be:
* Mashup Servers do not 'talk to each other'.
* You can, in Mashboard, see mashlets from different 'hubs' which is from different Mashup Servers.
* There are some potential ways to query multiple Mashup Servers, but a better more answer depends on the context in which you want to do this.
<!--Session data-->
Sara, technical writer/jackbe
My apologies for the delayed response, I have been away ...
We have a mashup server that we are querying to find out information about the mashlets that exist on the server. We have a partner who also has a mashlet server that we would like to query for information as well. Other partners may come through us to try and find information about both of the mashup servers (and possibly others in the future). What we would like to do, is be able to query our mashup server, and have it return mashlets from our server, along with our partner's server(s). We have been told that this is possible, but were not told how to go about doing it. We want to only have to know about 1 connection (the one to our mashup server), and just be able to configure that server to gather information from other servers so that it can present a combined view of the other servers it knows about.
If you can help me get this set up, it would be greatly appreciated.
I vaguely remember reading something about setting this up somewhere in the documentation, but I don't remember the term for it, so I am unable to find it. When reading, it seemed like it was a 5-step process, but the first thing was that you had to have an enterprise license, which we did not have at the time. We now have that, but I am unable to find the section of documenation that explained how to set things up ... Pointing me to that would help as well.
Well, my apologies also for not asking more specific questions. When you say "query and return mashlets" do you mean:
* return a list of available mashlets across Mashup Servers? This list then gets rendered in a UI you are designing? And if so, what do users do from this list once they have it?
* link to specific selected mashlets across Mashup Servers and render them in a page?
Mashboard in 2.7, does the last bullet point with one caveat -- you do have to know connection information to each Mashup Server. It sounds like that does not meet your needs, at least exactly as is.
<!--Session data-->
Sara, technical writer/jackbe
I am referring more to your first option. Currently, we are using the getMashlets service call, and it is working as expected. However, we would like to use the same call, to hopefully return a list of mashlets that exist not only on our server, but on others we are "connected" to.
Ok, so I found the documentation that I was referring to in an earlier post. It is in the Administration documentation, under the section "Configuring Chained Service Providers" (Presto Administration -> Mashup Server Configuration and Deployment -> Chained Service Access). I have an enterprise license (verified by looking at the "manage license key" option under Admin), but I do not see the "chain" option anywhere on the page after logging in, as listed in the instructions. Am I missing something?
Chaining is, unfortunately, not a good fit even if it sounds like it in the documentation. Mea culpa, but the docs are not up to date in this area and don't really cover some of the known issues with chaining.
One potential solution is to create a mashup in EMML that uses <directinvoke> to call that same internal service on the various Mashup Servers of interest and combine the results. You can then create a mashlet based on this mashup or write your own UI to invoke the mashup and get what you are after.
<!--Session data-->
Sara, technical writer/jackbe
We are just starting to use Presto, and we will have our own Presto server. Another group that we interface with also is using Presto, and it will have its own Presto server as well (on a different domain). Is there a way to configure our server to that it can "talk" to the other server? For example, if we query our presto server for a list of mashlets that have been created, we would like to also be able to see the list of mashlets that have also been created on the other presto server. Can this be done? If so, is this a one-way thing, or will our server update the other server while also being updated with information from the other server?
Again, not being very familiar with the configuration of the servers, I am not sure if this can be done, and if it can, how I would go about creating the configuration to set up the communication.
Any help that anyone can give is greatly appreciated.