Published on

Developing applications for access on mobile devices - or redeveloping existing apps - is a time-consuming process. We4IT docLinkr offers a simple alternative allowing you to take an existing application and, within one hour (actually this can be as little as 15 minutes), make it available on any smart device. Without writing any code. At all.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Vanessa’s introWe4IT have been around for over 10 years now, we’re IBM Premium Partners & Design Partners.  And we’re all about Notes, Domino, Traveler, Connections and all that good stuff.In Germany – that’s where our head office is - we’re best known for products for the German finance sector but we’ve also developed a range of solutions for the international market including Group Calendaring, Vacation Management, and a rather nice workflow modelling solution.We have some excellent product partners including Panagenda and Crossware.We’re big fans of xPages and 2 of our products are pretty much pure xPages apps - docLinkr (which we’re talking about today) and xBuilder which allows developers to configure their own xPages apps without doing any coding.Intro people:So that's We4IT. I'd also like to introduce Simon and I (Simon moves to photo slide).
  • Simon will be our presenter today- Simon is one of our technical consultants at We4IT and one of our gurus on all things mobile.And here's a lovely photo of me..... after many years of working together with Simon ;-) I am responsible for international sales and partner management at We4IT.Timing:Before I hand over to Simon I'd like to give you an idea of what we'll be looking at today.Simon is going to start by giving a brief overview of the subject of mobility and how this tends to look in the world of Lotus Notes.He will then give a demonstration of our product docLinkr.At the end you will have the opportunity to ask any questions you may have.The whole session should last about 45 minutes.We hope you enjoy it!And without further ado.... I'd like to hand over to Simon to get us started.
  • There are many organisations out there who need to get the data stored in their Notes systems out to their mobile users.We’ve all seen the incredibly rapid growth in the number of smart devices in companies. It started with BlackBerrys,and has moved on to devices with larger screens – iPhones, iPads, Android phones.These large screen devices can do more. And people recognise this.At first they were happy just to have email on their devices. But this is no longer true.Now they want access to the critical information stored in their customer databases, their teamrooms. And they don’t want to have to boot up their laptops to get it.
  • IT departments used to be able to hide behind a wall and say that company security means that they were not able to do this.But as many of us have seen, when senior people in the organisation bring in their iPads and ask us to put their Board Meeting database on it, they are more difficult to refuse.
  • Now none of this is new to you – I hope – but there is one critical factor that I want to highlight.If the situation that we see on this screen is all you have to deal with, if you are only being asked to expose one or two databases to your mobile users, then your are very fortunate.For many of us, the problem is that once people see that one person’s application has been mobilised . . .
  • . . . everybody else want their databases mobilised too.And if this isn’t happening to you now, it’ll probably happen next month or next year.I was talking to a development manager last week who is being asked to mobilise over 100 Notes dbs.And at the same time, they have to keep on developing the new apps that they’ve already committed to.And at the same time as that, they have to maintain their zillions of existing databases.Oh, and by the way, they’re not going to be given any extra resource for this.It’s worth considering how many databases you might be asked to mobilise, working out how much effort each will require and balance this against the resources available to you.Most of the other mobilisation solutions out there are very nice BUT they still require significant effort to mobilise an application.The way I see it is that if you’ve got the time, the skills & the resources, then redeveloping an application using XPages is great. And many people out there are doing just that.But I suspect that the way forward for many people will be to take a mixed approach. A select few apps will get the full XPages treatment with the rest – the majority - requiring a more rapid approach.And on the subject of XPages, there’s another factor. Some organisations – for whatever strange reason - are planning on moving away from Notes. And in this situation, in isn’t really appropriate to spend significant resouce on a platform that is retiring
  • When I say that mobilising databases using docLinkr is quick, I really mean it.A typical database could be exposed in an hour or two.In fact, I timed myself last week – I wanted to see just what was possible. And for a simple database – it was a journal db – I managed to do it – configuring one form and one view in under 5 minutes.I was talking to a brand new user last week who told me that they had mobilised 6 databases in one day.The reason it‘s so quick is because it‘s a process of configuration rather than coding.You can actually get a database out there without writing a single line of code. You can certainly increase the functionality of the application on the device by adding code to it, but this is optional.And it’s worth highlighting that you make no changes to the original nsf either.When enabling a database with docLinkr you simply choose which views from the original design you want exposed on the device, and which columns in those views. Then you say which forms from the original database should be visible and which fields in those forms.And, at its simplest, that’s about it.Pretty much all smart devices are supported. There are native apps for iOS and Android devices and the Blackberry Playbook.In fact there are 2 flavours of native app – one for smartphones called docLinkr & one for tablets called docLinkr HD.And BB phones are supported via webkit browser.And as soon as we find anyone using Windows Phone, we’ll support that too
  • In the current version no data is stored on the device itself although we will add the option to store & encrypt data in a release being made a little later this year.I have found it interesting that even if people are running corporate grade security like Mobile Iron on their mobile devices, many of them would prefer not to store data locally.Anyway, we’ll be providing our customers with this option soon.Naturally we respect the ACL and readers fields.Furthermore, additional restrictions are possible. Just because a user can edit particular fields on a document when they’re using Notes, you may choose to make that information read-only when they’re using a mobile device.
  • Let’s look at docLinkr’s architecture – it won’t take long because it’s very simple.docLinkr is comprised of 2 Notes databases. One on an internal server and one external – normally in the DMZ.No new servers are needed, no server tasks and – I think I already mentioned, no coding.CLICK Here are your existing Notes databases.The docLinkr configuration database CLICK is also located on an internal server – any server will do as long as it can see the databases you would like mobilised. This is where you do the work of configuring the database you want published.On some external server – perhaps the Traveler server if you have one CLICK – is the Connector database. This contains the XPages code and the web services that we use to make docLinkr work.So, mobile devices CLICK using docLinkr’s native app or, indeed a PC or a mobile device using a browser connect to the Connector database which, in turn, requests data from the docLinkr internal db which then passed back to the device.As you can imagine, implementing this is pretty simple.
  • Now it’s time for a CLICK short demonstration . . . (leave next slide on for a few seconds)
  • Sorry – wrong sort of demonstration
  • docLinkr is completely free for an unlimited number of users for databases based on standard templates – by which I mean Jounals, Teamrooms, Discussions and the Domino Directory.For other databases we are happy to provide free trial versions and will support you in mobilising you first applications.You’ll be happy to hear that docLinkr is extremely good value with an entry level price of €1125 for up to 25 users. It gets cheaper for larger numbers of users.
  • After questions:“So, if that’s all; Vanessa would you like to wrap this up?”
  • Thank you Simon for presenting the webinar.And thank you to everyone in the audience for your questions, there were some good ones there.You're also very welcome to download these files from Slideshare- if you don't know Slideshare the link is integrated into our homepage.I would just like to wrap up the session for today, by saying thank you very much for your time! If you have any further questions you'd like to ask, or if you'd like to test docLinkr yourself, please don't hesitate to contact Simon or I directly.You can also sign up for our newsletter by going to www.we4it.comAnd that's it from us..... thank you and goodbye!

    1. 1. We4IT docLinkr Mobilising Lotus Notes® Applications. Without Coding.Simon Peek Technical ConsultantVanessa Hutchinson Sales & Partner Manager
    2. 2. This Is What We Look LikeMastertitelformat bearbeiten
    3. 3. Application MobilisationMastertitelformat bearbeiten
    4. 4. Application MobilisationMastertitelformat bearbeiten
    5. 5. Application Mobilisation docLinkrMastertitelformat bearbeiten
    6. 6. Application Mobilisation docLinkrMastertitelformat bearbeiten
    7. 7. We4IT docLinkr• Rapidly Mobilise Notes databases• No Coding Necessary• No Need to Change Existing Databases• For All Smart Devices* docLinkr*Windows Phone will be supported as soon as anyone asks us to!*Android pre-2.1 not supportedMastertitelformat bearbeiten
    8. 8. We4IT docLinkr• Secure – No Data on Device• ACL Respected• Additional Restrictions PossibleMastertitelformat bearbeiten
    9. 9. We4IT docLinkrMastertitelformat bearbeiten
    10. 10. DemonstrationMastertitelformat bearbeiten
    11. 11. DemonstrationMastertitelformat bearbeiten
    12. 12. DemonstrationMastertitelformat bearbeiten
    13. 13. LicencingMastertitelformat bearbeiten
    14. 14. Questions?Mastertitelformat bearbeiten
    15. 15. Contact @simonspeakeasy vanessa.hutchinson@we4it. com @vanessahutchin3Mastertitelformat bearbeiten