as long as BMC takes ownership of this, and either ensures it is part of their product.. Lets not get another third part involved.. Flash is too much already.. It really makes the Gov and security mad, and makes the possibility that BMC will not be used in the future.
Flash has had security issues, and to make BMC dependent on this is not a good idea. Security folks will balk and say no if BMC adds another dependence on another company, do yourself a favor BMC - Buy flash or this other new product so you can control it and package it yourself.. PLEASE PLEASE do us and you a favor.. My 2 Cents. On Tue, Jul 13, 2010 at 8:35 PM, Easter, David <[email protected]> wrote: > ** > > It expected that there will be a *DBC interface to AR System in future > releases. That interface will not be provided through a Remedy User client > for the obvious reason that the client will not be distributed. > > > > That aside, a different method for integrating with desktop client side > applications will be considered that would emulate things done currently > through OLE/DDE (and potentially ODBC to a certain extent). The goal will > be to ensure a needed capability is fulfilled and will not be driven by a > desire to retain or utilize a specific technology – which is why details > cannot be provided. This is what the FAQ is saying. > > > > -David J. Easter > > Sr. Product Manager, Enterprise Service Management > > BMC Software, Inc. > > > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Shellman, David > *Sent:* Tuesday, July 13, 2010 2:46 PM > > *To:* [email protected] > *Subject:* Re: Statement of Direction regarding EOL of Remedy User client > has been amended. > > > > ** > > LJ, > > > > When I initially read the reply I had the same reservations you were > having. It seemed that Dave's response was that the ODBC driver was also > going away. My reply was a wish/hope that the ODBC driver be continued > under that portion of the statement. > > > > When reading Dave's reply to your question, it seems to be a completely > different reply concerning the ODBC driver. > > > > So now I'm confused. Was Dave's reply to my ODBC driver question a general > response to integration questions? > > > > I guess I'll need to take a deep look at the statement. > > > > Dave > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *LJ LongWing > *Sent:* Tuesday, July 13, 2010 5:36 PM > *To:* [email protected] > *Subject:* Re: Statement of Direction regarding EOL of Remedy User client > has been amended. > > ** > > Ah….that’s the part I wasn’t getting….see…it’s easy to overlook things when > in a hurry J > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Shellman, David > *Sent:* Tuesday, July 13, 2010 3:00 PM > *To:* [email protected] > *Subject:* Re: Statement of Direction regarding EOL of Remedy User client > has been amended. > > > > ** > > In the past Remedy admitted that reporting functionality in the desktop > client was weak. Other reporting tools like Crystal were suggested as the > way to go to get "pretty" reports. It seemed that the ODBC driver was > provided as a way to access the data using tools like Access, Excel, perl > and even Crystal. The AR System ODBC driver also enforced permission access > on the forms and data. It is fairly easy to show folks how to set up the > ODBC driver and setup Access, Excel to link to the data. It seems to me > that replacing this process with Web Services or automated reports through a > web client is not going to be simple. > > > > Hopefully "BMC is investigating methods to enable interaction between > local applications while ensuring that security concerns are met" will > continue to consider the use of an ODBC driver. It's not perfect (limits on > join through the driver between two forms) but it does provide a standard > connection for access to data. > > > > Maybe my concern just deals with change and not really understanding how > future processes can used to easily connect to the AR System data using > Access, Excel, etc. > > > > Dave > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Easter, David > *Sent:* Tuesday, July 13, 2010 4:17 PM > *To:* [email protected] > *Subject:* Re: Statement of Direction regarding EOL of Remedy User client > has been amended. > > ** > > Hi Dave, > > > > This is answered in the FAQ section of the Statement of Direction. > > > > 1. I have created an integration with the Remedy User client. Will > that integration still be supported in the major or minor versions after AR > System 7.6.03? > > 2. No. Because the Remedy User client itself will become > unsupported, integrations with the Remedy User client will also become > unsupported. BMC recommends that you consider creating an integration that > works properly with the web client and BMC Remedy Mid Tier prior to the end > of life for the Remedy User client. > > 3. How will the client provided in future versions interact with > applications local to the user’s desktop OS? > > 4. Traditional OLE or DDE integrations will not be supported. > However, BMC is investigating methods to enable interaction between local > applications while ensuring that security concerns are met. Details are not > available at this time. > > 5. Where can I get assistance creating or implementing integrations > for use by the web client? > > 6. A good source of assistance is the BMC Developer > Network<http://communities.bmc.com/communities/index.jspa>, > specifically the BMC Remedy AR System > forum<http://communities.bmc.com/communities/community/bmcdn/bmc_atrium_and_foundation_technologies/bmc_remedy_ar_system> > . > > > > There have also been previous conversations here on the ARSList about being > able to replicate the functionality on the web client using Javascript for > many of the existing integrations done on the desktop client. > > > > -David J. Easter > > Sr. Product Manager, Enterprise Service Management > > BMC Software, Inc. > > > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Shellman, David > *Sent:* Tuesday, July 13, 2010 1:01 PM > *To:* [email protected] > *Subject:* Re: Statement of Direction regarding EOL of Remedy User client > has been amended. > > > > ** > > David, > > > > You may not be able to answer this question here. I'll through it out > there any way. > > > > We have a number of automated and manual processes that connect to the AR > System from Access, Excel, perl, etc through the AR System ODBC Driver. > With the desktop client coming to an end of life after 7.6.03 will there > still be an ODBC driver or we need to look at an alternative solution in the > future. > > > > Dave > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
