Answers below along with the following. Once a server has been setup as a Hub, it does not function like a normal ARS server and therefore you would not be able to achieve your requirement OOB. A good idea, but currently not possible without customisation.
A Hub limits what can be created once it has been configured. The consoles perform differently and re-direct users to the various Spoke systems for requests that have been generated from these servers. It is a central viewing point for all systems in the "Wheel" so to speak. Although a full server, it is designed not to have data created in it just a viewing portal to other systems. That is the concept (although I would think that you can indeed create data). _____ Kind Regards, Carl Wilson http://www.missingpiecessoftware.com/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Pierson, Shawn Sent: 05 November 2013 13:33 To: [email protected] Subject: Hub and Spoke for Non-Production ITSM Systems ** Good morning, I wanted to throw this out there for feedback. Most of the functionality for hub and spoke in ITSM seems focused on using it between various production environments between different groups that have their own Remedy systems within an organization. My company currently has one production Remedy instance and we're probably going to be fine with that for the next year at least. However, I was thinking that this may be useful from a non-Production system standpoint. What I'm thinking is that I set up the Production server as the hub, and my development and test environments as spokes. This should help keep my foundation data fresh between all of the systems. However, I have a few questions that will determine whether or not it will work: 1) Can you implement hub and spoke without buying DSO licenses (e.g. is DSO now included or is it still a separate product?) - Included 2) Can you control what data is synchronized between the hub and spoke servers? (e.g. can you exclude Production notifications from the sync?) - Foundation Data is synchronised from the Hub > Spoke, first sync initiation is manual, then the system automatically syncs data for Companies designated as "Service Providers" (although I have heard that other non "Service Provider" data has been synced before along with the designated Companies). It does this using generic DSO mappings and a round robin approach to synchronisation. Spoke ITSM request data is then sent back to the Hub for the Companies designated "Service Providers". Any Company locally configured on a Spoke keeps its data and configuration local to the Spoke. So in the Hub you see all requests (subset of data) from the Spokes for these Service Provider Companies, then you drill down to the Spoke via URL redirects to the actual Spoke. You could also mark the data as synchronised using the DSO fields so it is not updated. 3) Is it possible to remove the relationship temporarily, keeping the data on the spoke server, in such a way that you can test certain data/configuration changes without it being overwritten from the hub? - You can remove the Hub > Spoke configuration, but the rules in the DSO are configured as generic and the mappings would need to be turned off to limit the data exchanged. 4) Is it possible to push data from the spoke back up to the hub? - The only data heading back to the Hub is the subset of ITSM request data for display in the Consoles - customisation would be required to send other data. 5) Are there any other potential risks from adopting hub and spoke to keep non-Production systems up to date? - currently not designed for this functionality (although with some changes would work well) This isn't a critical thing for me, more of a discussion point, but if it works it could save us all a lot of effort especially around keeping test and production systems similar. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Private and confidential as detailed here <http://www.energytransfer.com/mail_disclaimer.aspx> . If you cannot access hyperlink, please e-mail sender. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
