Jiri, Actually, the idea of establishing a traditional VPN and accessing the dev tools via the tools server is being phased out. BMC is now using a technology called "client gateway." It opens a secure tunnel from source and destination and allows access to RoD infrastructure almost as a local resource. So as a developer, you can have your dev tools running on your own laptop and connect to your dev environments in RoD. Same works for your integrations to on premise systems.
Sent from my iPhone > On Oct 9, 2015, at 5:06 AM, Pospi ARSList <pospi.arsl...@gmail.com> wrote: > > ** > Hi Joe, > > I have come across another area that you may consider as a limitation, though > not caused by the product itself, but the fact that the environment resides > outside of the customer’s corporate infrastructure. > In this scenario, you want to pull data to Remedy using AI, say from SCCM > database. You obviously need to open firewalls and set up connectivity from > Remedy DEV, QA and PROD servers to your corporate network. Standard thing, no > problem here. > Then you want to start developing your transformations in Spoon. Spoon in RoD > can only be run from so called Tools server (aka jump server allowing direct > access to the AR Server box). > Tools server, however, does not have connectivity to your corporate network > as the firewall/VPN rules are only set up for your DEV,QA and PROD. > Now, you have two choices – employ BMC professional services to do the work > for you (as they can access directly the servers) or open discussion with RoD > operations team about the possibility to have direct access to the DEV server > for yourself or to have connectivity enabled from Tools server to your > corporate environment (may not be something your security will be happy as > the tools server is not exclusively allocated to your company). > > Apologies about somewhat long-ish post, but from my current experience, this > area is not particularly well understood/documented and made clear in RoD > environment. > > Kind Regards > Jiri Pospisil > > From: Joe D'Souza [mailto:jdso...@shyle.net] > Sent: 08 October 2015 22:12 > Subject: Re: RoD limitations... > > ** > Thank you Doug for clarifying this limitation. > > The last time I heard about it, I interpreted it as it was restricted > completely from the product – did not know that there was a scope to discuss > this with the On Demand team. > > So basically it does look like there is no difference on any features at all > – just a difference in operation policies. > > Thanks again. > > Joe > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug > Sent: Thursday, October 08, 2015 3:26 PM > To: arslist@ARSLIST.ORG > Subject: Re: RoD limitations... > > Joe and LJ, > > There is a difference about what the product will allow vs. not allow and > what the operation environment policy allows or not. > > There is no restriction in the product. The product in RoD is identical to > the product that is available On Premise. Both the features you mention Joe > are fully supported – and used by the applications – both On Premise and On > Demand. > > Now, if you are running the environment On Demand and want to add new logic > that uses these features, there are restrictions. Remember, the BMC team is > responsible for running the environment and making sure it is up and running > and safe. If you do a run process that is running some external process or > issuing direct SQL commands that are outside the AR System control, there are > issues about data security and integrity and about what processes are doing. > On Premise, you are responsible for your own environment and processing so > you can take responsibility for the issues here. The On Demand team however > has to be very conservative about what they are allowing a customer to put > into an environment that they are responsible for operating. > > So, in general, the operations of Direct SQL and Run Process are not allowed > within a RoD environment. If there is a requirement for these operations, > you have to have discussions with the RoD team about what is possible or not > within the environment. > > In the end, not a product or feature issue, but an operational > issue/discussion. > > Doug Mueller > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza > Sent: Wednesday, October 07, 2015 3:38 PM > To: arslist@ARSLIST.ORG > Subject: Re: RoD limitations... > > ** > I have not directly worked in an RoD environment, but when the product was > new-ish, somewhere around version 7.x, I had tried to research as to the > differences and limitations and that is what I was told – that everything is > the same. The only difference feature wise was these two and these two were > removed for security reasons or something like that so that you could not > execute scripts directly on the DB or programs directly on the server. I was > also told that that was a basic architecture of most cloud solutions during > that time where you did not have any kind of direct control on the underlying > DB’s or OS. > > So assuming that things change, ideas evolve, systems get smarter, (users get > dumber J ), I was wondering what has changed. > > In fact it would be nice to know what were the differences between the two as > the versions advanced from the time RoD was first born.. > > Joe > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing > Sent: Wednesday, October 07, 2015 6:25 PM > To: arslist@ARSLIST.ORG > Subject: Re: RoD limitations... > > ** > Really? I didn't realize that BMC was producing anything other than a hosted > Remedy...didn't realize that there were limitations to what the system could > do.... > > On Wed, Oct 7, 2015 at 3:29 PM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > I had raised this once a long time ago to get a sense of what flavor from the > full version would a Remedy on Demand solution loose and there were pretty > much 2 key features that I recall. > > The inability to issue a Direct SQL within workflow > The inability to issue a Run Process within workflow > > With 8.x, and 9.x, are there anything more or less that is lost feature wise? > > Joe > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: > "Where the Answers Are" and have been for 20 years_ > _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"
