1. WMarket For Adminstrators Manual Installation

2. Basic Dependencies To install your own WMarket instance, you are required to install the following software: – MySQL 5.5 – Java 7 – Tomcat 7 You can install them with the packages manager offered by your Operating System: – Ubuntu/Debian: apt – CentOS: yum 2

3. Creating the Database Before installing WMarket, you must create a database within your MySQL installation. To do so, run the following command: Don’t worry about the tables creation. WMarket will do it for you when you deploy it 3 mysqladmin –u root –p[PASS_ADMIN] create marketplace

4. Getting the WAR file In the attached page [1] you can find the list the Web Archive files generated for the different WMarket versions – Choose the version that you want to install – Download the corresponding WAR file [1] https://github.com/conwetlab/WMarket/releaseshttps://github.com/conwetlab/WMarket/releases 4

5. Configuring the Database To configure the database properties, modifiy the WEB-INF/classes/properties/database.properties file contained in the WAR file: –jdbc:url : The path where the marketplace database (the one you created previously) is available –jdbc:username : A MySQL user with read/write rights in the selected database –jdbc:password : The user’s password 5

6. Configuring the Indexes WMarket uses Lucene indexes to perform better searches These indexes must be stored in the local file system You can modify the path used to store these indexes by modifying the WEB- INF/classes/properties/marketplace.properties file contained in the WAR file: –luece.IndexPath : the file system path where the Lucene indexes will be saved 6

7. Configuring the Media files WMarket allows users to upload media files (Store images…) These files must be stored in the local file system You can choose where these files are stored and their maximum size by modifying the WEB- INF/classes/properties/marketplace.properties file contained in the WAR file: –media.folder : the file system path where the media files will be saved –media.maxSize : the maximum size of these files 7

8. Configuring Descriptions Autoupdate Period WMarket can check registered descriptions periodically to obtain new offerings You can set up the period used to check the descriptions by modifying the WEB- INF/classes/properties/marketplace.properties file contained in the WAR file: –descriptions.updatePeriod : the period used to check if new offerings have been included in the registered descriptions 8

9. Configuring OAuth2 (1) By default, WMarket uses a local authentication system (local system). To use and FIWARE IdM: – Register your Wmarket instance in the FIWARE IdM: Callback URL: http://[WMARKET_HOST]:[WMARKET_PORT]/WM arket/callback?client_name=FIWAREClient Roles: create a new role for providers. You can choose any name for this role. You will need this name later. 9

10. Configuring OAuth2 (2) Modify the WEB-INF/classes/spring/config/BeansLocations.xml file contained in your WAR file: – Replace – By Set up the OAuth2 properties by editing the WEB- INF/classes/properties/marketplace.properties file contained in the WAR file: –oauth2.server : the IdM server https://account.lab.fiware.org (GI) https://account.lab.fiware.org –oauth2.key : the client ID returned by the IdM at the time of registering the application –oauth2.secret : the client secret returned by the IdM at the time of registering the application –oauth2.callback : http://[WMARKET_SERVER]:[WMARKET_PORT]/WMarket/callback –oauth2.signOutPath: auth/logout –oauth2.providerRole : the name of the role you created in the last step 10

11. Deploying the WAR Save your WAR file with all the changes you have introduced Copy the WAR file into the webapps folder of Tomcat. – Ubuntu: /usr/lib/tomcat7/webapps – Debian: /usr/share/tomcat/webapps 11