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 space Katya Todorova March, 2011

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

3. The problem – Store management Corporate headquarters Store n Store 1

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)

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

11. Update

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)

19. Configure the address of the store server

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

22. Corporate server app notifies relevant store servers

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 Todorova katya.todorova@sap.com