It’s not specific PHP but with this release I’d imagine we will soon be seeing the new PHP connector coming out as well, NetWeaver RFC gives the Next generation Ruby and Perl Connectors, even though it’s Ruby and Perl it’s certainly worth taking a look at that’s for sure!
There’s been a lot of activity around this part of things lately and we are already seeing the connectors now being developed to handle both SOA as well as the RFC, and what’s even better:
RFC is a stable technology, and has been for many years, so I can understand why this revelation may not seem very exciting. What is exciting is the unprecedented level of cooperation, understanding and good will that has come out in a relatively short time, as I have moved through the process of redeveloping the Ruby and Perl RFC Connectors. The result is (and will be more so), a better fit in terms of how the SDK works with Dynamic Languages, allowing the API that the Dynamic Languages offer for RFC connectivity, to better reflect the nature of those programming languages. For example – there are better features in the new NW RFC SDK that allow for easy translation of ABAP types to Ruby/Perl types.
So as you can see many a new change coming to the world of SAP and Scripting Languages!
What’s this? Seems that some folks over in the SAP Developer Network (SDN) are working on a new framework for SAP and PHP, the SAP Network Wiki is a being developed as complete transaction based framework around the SAP transactions.
As you may see…My main goal is to develop an SAP PHP based Framework, name it SAPHP, or something else. Of course, a lot of work must be done and a lot of things must be improved…For example:
- SE11 –> Be able to create Tables, Domains, Data Elements.
- SE10 –> Be able to create new Transport Orders.
- SE38 –> Be able to create programs and save them on SAP.
- ST22 –> Be able to read the Short Dump information.
Something to take a peek at and maybe keep one eye on for awhile to see where it goes…
It seems that James finally got around to blogging about something he saw. He talked a bit about it during one of the RedMonk Radio episodes but did not even scratch the service leaving me sitting ask “What the…” but finally he blogged it and will hopefully be sending over the “deets” from Andrew soon.
James saw a presentation from T-Mobile and how they developed (rather quickly) an app using Adobe Flex. Now I like Flex (I too can get down with Flex) and I’m hoping to add a “Flex” forum to SDN here in the near future (any Adobe guys want to help moderate?) and since I’ve been pushing the use of Scripting Languages his post is right up my alley in fact in more ways than one.
I’m not going to comment on SAP’s UI strategy, Filip did that and Thomas just reminded everyone of that and raised a few more comments, nor will I comment on what Dan said about SAP’s UI, not that I don’t have an opinion it’s just…
In the current issue of the International PHP Magazine their is a very nice tutorial done how connecting PHP with SAP, those who attending the Las Vegas SAP TechEd might have seen this tutorial for those who missed it there I highly recommend checking out the current issue and take a look.
It combines the basics of PHP and AJAX with the power of an SAP backend, the beauty of the tutorial is the ease of use and the hint of what is possible with the versitility of PHP and the flexibility of SAP.
I put together a little package not to long back called “Scripting in a Box“, it was built with the idea of taking the guess work out of connecting various scripting languages, e.g. PHP, with SAP and seeing some of the thing possible.
Well last month in the International PHP magazine it was a featured review! Check it out!
This is a required patch for v0.1 of Scripting in a Box, please download this patch. This patch repairs the error not allowing one to start/stop and restart the Apache server process through Eclipse.
Also added is a optional check on the http://localhost:8080 index page to check for updates.
It has also been mentioned by a few users there is a problem when attempting to install new components or update exisiting plugins in Eclipse, it seems the following file missing: c:Developmenteclipsefeaturesorg.rubypeople.rdt.source_0.8.0.604092300RC1feature.xml simply copy the feature.xml from C:Developmenteclipsefeaturesorg.rubypeople.rdt_0.8.0.604092300RC1 to C:Developmenteclipsefeaturesorg.rubypeople.rdt.source_0.8.0.604092300RC1 and that should solve the problem.
I get this question a lot, and in fact since SDN is becoming more noticeable in the outside world and the fact that we have a growing and strong community and a decent size library of information, the question seems to be popping up more and more of late.
Well the bottom line is this, and I know that if someone really wants to make me look bad they’ll post this way out of context, “You should not use PHP in your SAP Landscape”, now the rest of it for those of you interested in the whole story. You should not use PHP in your SAP Landscape if you don’t already have it. No one, myself nor SAP is actually telling you to run out and learn everything you can about PHP. What is being said is simply this, “if you have PHP already in your landscape you don’t need to run out and learn something else”.
A lot of times someone will hear that they are installing SAP so they do a search and find all this information related to ABAP, Java, .NET so on and so forth so they think that all that work they’ve already done in PHP for their internal applications will have to be redone, removed or replaced. This is simply not the case, and that is the message I’ve been trying hard to get across. If you have PHP knowledge in house already and add SAP to the mix then you can still leverage that PHP knowledge and do not need to retrain all your developers in something other than the basics of how a SAP system works.
In fact with the release of NW04s the support for Web services is tremendous and therefore might make life even a little easier for your developers.
OK this was a lot shorter than I was thinking but I don’t want to confuse the bottom line message with clutter.