I just read Justin James’ most recent diary entries, where he continues to develop his Rat Catcher web application; his next challenge – to integrate custom code, he’d already developed, into OutSystems. As Justin said, “I was not worried — after all, I knew that Integration Studio would let me hook up my application to this code.”
I thought I’d share some key learnings and highlights from these two journal entries.
Integrating Web Services
Turns out Justin’s code uses some advanced patterns, and although Integration Studio did its part and “was successful at a technical level,” Justin opted to use another form of integration: Web Services. As soon as Justin made his code available as a web service “it was a cinch to point Service Studio to the deployed Web service.” Well, Justin did find a little bug, but this was a great opportunity for him to connect with the OutSystems community
for help and guidance, and we’re really happy that he thought “it was a great experience”!
Deploying Rat Catcher
With all the pieces in place, it was now time to deploy the first public version of Rat Catcher. Justin has a pretty elaborate infrastructure, and the experience he documents in the diary entry will surely help people with similar setups. Nice to hear that installation was a breeze, since “the team did an amazing job with version 5 and getting the install to be smooth and easy.”
Doing things the hard way – but learning…
After configuring the Agile Platform, all that was left was deploy the application. Justin actually did this the hard way; he deployed one component at a time… but I was really happy to see that he learned all about the OutSystems solutions, so he is now able to quickly move all components to production at once, while keeping version records so he can rollback to old versions if needed.
I’m looking forward to the next five installments to hear about his continued experience with the platform, and hope you’re following along too. What do you think of Justin’s experience so far?