This document discusses using p2 to manage software updates across multiple retail store locations. P2 provides capabilities for initial installation of software, updating existing software, and propagating configuration changes across stores in a way that does not require synchronization between stores or extensive maintenance. When a store server is first set up, p2 installs the necessary software applications from a local repository populated from the corporate server. When updates become available, the corporate server notifies store servers to update their local repositories and applications as needed, and to propagate any new configuration settings to devices.

1. Updates in the micro spaceKatya TodorovaMarch, 2011

2. p2“Simple things should be simple. Complex things should be possible ”

3. The problem – Store managementCorporate headquartersStore nStore 1

4. Store management - requirementsNo synchronized update of the stores

5. Need to be able to install the server/device apps

6. Create a store with minimal configuration

7. No / minimal maintenance

8. The device can be of various sizes (from GB to MB)

9. The device has no state Store management scenariosTechnical scenarios: Initial install

10. Takes the server out of the box in the store and needs to get setup

11. Update

12. Checks for newer version of server softwareBusiness scenario:“configuration propagation”

13. Changing the configuration of the device (we are using ConfigAdmin)Store management and p2p2 repositoryRT basic package(p2 on top of equinox) Running in the process of the appRT basic package Running in the process of the app

14. Initial install with p2Corporate server initial provisioningMake p2 repository availableStore serverUnpack the server

15. Start it up

16. Configure the address of the corporate server (aka repo)

17. Configure the name of the app (store type  the product IU)

18. Invoke p2 director to install the server productDeviceStart it up

19. Configure the address of the store server

20. When it boots p2 installs device product from store server local repositoryUpdate / propagate configuration with p2Corporate server initial provisioningOut of scopeStore serverAn update is done to the store server app

21. The corporate server repository is updated with the new content

22. Corporate server app notifies relevant store servers

23. Each store server decides when to apply the changes publishes new POS configuration if anyupdate server app DeviceInstalls updates from server p2 repository (device app binaries)

24. Generates new IU component corresponding configuration changes Summaryp2 has a lot of basic building blocks to take care of the complete problemdirector / engine for the RT side of things

25. publisher for the “development”

26. application (e.g. director app)Don’t hesitate to engage with them on the ML, they don’t bite

27. Thank You!Contact information:Katya Todorovakatya.todorova@sap.com