W
whenshaw
Guest
As Bill Wood pointed out, your REST service that provides the marketing information would be set up as a different web application from the one that you already use for the app's main data, with its own JSDO catalog and authentication model. The marketing REST app would need to use the Anonymous authentication model. As for the steps involved to support two OpenEdge endpoints: You would use the Mobile App Builder to add a second "Session service" to the mobile app, separate from the MobileService_Login/MobileService_Logout group that you already have. You could call it something like MarketingService_Login (and MarketingService_Logout). Execute MarketingService_Login when the app first loads, which would establish a connection only to your marketing service, create a JSDO for the marketing data, and get the marketing data that way. Your should not need to change your existing use of the MobileService_Login service. Please be aware that we expect to release a new version of the Mobile App Builder very soon (but you would need to check with Product Management for exact timing). The new version of the MAB uses a somewhat different model for working with Session services, and makes it easier to create additional Session services. Currently you would need to create the second group of Session services by copying your existing service or using a plug-in, but our plan is that the process will be much easier in the new release. Please let me know if you would like more details on using a second Session service with the current MAB. Good luck! -- Wayne Henshaw
Continue reading...
Continue reading...