I think this is a healthy debate, and I'd like to see it unfold a little more. Some people seem interested in this remaining a purely community-driven (with some contribution and participation by SAP) effort, while others want this to be "official" SAP software (with all that implies regarding support, licensing, etc.). If you'd like to speak more directly, check out my business card and send me an e-mail - or even better, meet up at SAPPHIRE Orlando, take home some "goodies," and let's see what we can decide together. SAP wants to support the scripting community(ies), and we are getting started in figuring out how we can make our greatest contribution - by listening to you. More important - the scripting language community around SAP seems to be growing and vibrant. Perhaps a small point, but in addition to tireless SDN staff posting here, you have the president of the SAP Product and Technologies Group (Shai Agassi) and a senior exec reporting to Shai (me) participating here. If this is the case, what is ultimately SAP's intention with punting this technology on SDN? Are they trying to suss out the feel and whether there is enough interest so as to make a decision about developing add-ons themselves that make use this technology? It will therefore remain in the domain of the developers, who may develop solutions under the radar, but cannot expect buy-in from their IT managers, because there is no official support for these solutions. My argument is that because SAP did not develop these connectors and will therefore most probably not support customers who have problems with them (again, I'm talking official support), it will be more difficult to get buy-in from customers to make use of these technologies. The kind of support I'm talking about (and hence I say "official support") is being able to get support from SAP on those connectors via Service Marketplace. I'm not sure I follow the second part of your sentence. That should be it, Python and Ruby/Ruby on Rails are already in the works! Discuss “Scripting in a Box” Download: Scripting in a Box on SDN or in a LIVE Scripting in a Box v0.0.1 Once you’ve unpacked it to the root of your drive then you can run the “configure.vbs” file which will ensure that it is ready to run from the drive location, change a drive location run the “configure.vbs” again otherwise just run the “start.bat” file from then on. ![]() Unpack then the RAR file to your C drive or whichever drive (USB stick works as well). Contentsīasically after you download the package and unpack the ZIP file you will find the “readme.txt” explaining a few things and making sure you know I am not responsible if something really bad happens □ and a RAR file which is also a form of archive like ZIP. ![]() The only thing you need to supply is a SAP system such as the one available for download here on SDN. With this first release of “Scripting in a Box”, that is version 0.0.1 you are given a full development environment. You know your environment so you can try out PHP or Perl development with SAP. It’s actually my first community contribution dealing with technology in awhile so it’s nice to be back in the “game”, so what did I do and what am I babbling about? Well I decided to devote the little free time I have these days to creating a solution for all of you out there who are having difficulties getting your Scripting Environment setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |