![]() This file contains a number of configuration options. The EMFStore server will create an es.properties file with the default configuration if it cannot locate an es.properties file on startup. Configuring server properties in es.properties We will provide more detail below on these files. Furthermore, there is a file named emfstoreServer.keystore, which contains the SSL certificate of the server. On the data folder root level, there is a file s, which contains references to all projects stored on the server. There is a folder conf that contains the es.properties by default and can contain additional property files. For every project, there is a project folder project. Independent of where the data is stored, the layout of the data folder is as follows. All data will now be stored in /server/profiles/.Īlternatively, you can also provide a custom implementation for defining the folder where data is stored in by implementing an ESLocationProvider and registering it at the .server.locationProvider extension point of the .server plugin. The home directory can be changed by setting it with the program argument -EMFStoreHome=. Data will then be stored in /.emfstore/server/profiles/. The profile name can be changed by setting it with the program argument -profile=. ![]() This can be changed by different configuration options:Ĭhanging the EMFStore home directory by a program argumentĬhanging the Location Provider implementation All of the server’s data is stored by default in /.emfstore/server/profiles/default. In this part of the tutorial, we will discover configuration options of the EMFStore server. So far we have not changed any of the default behaviors of the server. ![]() We will discuss how to configure these parameters at the server in the next section.Īt this point, you can run all the example steps as described in the tutorial “Getting Started with EMFStore” but, this time, with a server that is not embedded in the client and with two different clients. The preconfigured default certificate should not be used in production since its private key is publicly available in the EMFStore source code repositories at and in every EMFStore build.Īll these parameters can be changed at the server. Finally, a certificate for SSL encryption can be selected and imported. Next, you can enter a name to display the server in the repository view. New Repositories (Servers) can be added with the plus button.Ĭhoose ‘EMFStore’ as provider and configure the URL (DNS name or IP address) and port of the EMFStore server. The default super-user credentials are ‘super’ (username) and ‘super’ (password). To connect the clients with the server, we can log in to the Local Server that is already configured in the repository browser. The two clients each open a new workbench. The server will launch headless and produce output to the console view in the Eclipse IDE. Now we can launch the three configurations. emfstore folder since it can be re-created on demand. If you do not need the EMFStore client and server-related data anymore, it is safe to delete the entire. To reset all data in clients and servers, it is often useful to delete the client and server data directories. All data is stored in /.emfstore/server/profiles/ and the default for is also ‘default’. Otherwise, the server behaves quite similarly in default configuration. Since we only start one server, we do not need to set profiles like we do for the clients. To set up a server, you follow the same steps but select a different application shown on the screenshot. Since we want to let the two clients store their data in different locations, we can configure the profilename by adding -profile=democlient1 and -profile=democlient2, respectively, to the program arguments in the launch configuration. The default behavior of EMFStore client API is to store data in /.emfstore/client/profiles/. To set up a second client, you can simply follow the same steps and assign a different name to the launch configuration. We use the EMF Client Platform as a demo application in this context, so you do not need to implement a client by yourself to follow this tutorial. Using the tutorial “Getting Started with EMFStore”, we can set up a first client based on the EMF Client Platform e3 application. Running an EMFStore Server and Clients in the Eclipse IDE
0 Comments
Leave a Reply. |