|
1 | 1 | # interference |
2 | 2 |
|
3 | | -##### Interference is a java library enable you to run a full featured ORM database |
4 | | -##### and implement persistent layer in your distributed application |
| 3 | +##### java-based distributed database platform |
5 | 4 | ###### (c) 2010 - 2020 head systems, ltd |
6 | | -###### current revision: release 2020.2 |
| 5 | +###### current revision: release 2020.3 |
7 | 6 | ###### for detailed information see: |
8 | 7 | ###### http://interference.su and doc/InterferenceManual.pdf |
9 | 8 | ###### contacts: info@inteference.su |
@@ -39,9 +38,11 @@ Consider a basic example when the interference service used as a |
39 | 38 | local persistent layer of the application and runs in the same JVM |
40 | 39 | with the application. |
41 | 40 |
|
42 | | -To get started with interference, you need to include the interference.jar |
43 | | -library in your project configuration. For maven pom.xml, this might look |
44 | | -like this: |
| 41 | +To get started with interference, you need to download sources of |
| 42 | +the current interference release (2020.3), build it and install it |
| 43 | +into your local maven repository (mvn install). |
| 44 | +include the interference.jar library in your project configuration. |
| 45 | +For maven pom.xml, this might look like this: |
45 | 46 |
|
46 | 47 | ``` |
47 | 48 | <dependencies> |
@@ -72,39 +73,3 @@ Next, specify the necessary set of keys in the project |
72 | 73 | -XX:ConcGCThreads=4 |
73 | 74 | ``` |
74 | 75 |
|
75 | | -To run a single local interference node, you can use the standard |
76 | | -supplied interference.properties configuration. Note that file |
77 | | -interference.properies should be within /config subdirectory. |
78 | | -Next, see the configuration section. |
79 | | - |
80 | | -Then, add following code into initializing section of your java application: |
81 | | - |
82 | | -``` |
83 | | -Instance instance = Instance.getInstance(); |
84 | | -Session session = Session.getSession(); |
85 | | -instance.startupInstance(session); |
86 | | -``` |
87 | | - |
88 | | -where Instance is su.inteference.core.Instance and Session is su.interference.persistent.Session. |
89 | | - |
90 | | - |
91 | | -## Service as standalone |
92 | | - |
93 | | -This option can be used when the cluster node is used solely for the purpose of further horizontal scaling of the data retrieving mechanism: |
94 | | - |
95 | | -``` |
96 | | -java -cp interference.jar |
97 | | --Dsu.interference.config=interference.properties |
98 | | --Dcom.sun.management.jmxremote |
99 | | --Dcom.sun.management.jmxremote.port=8888 |
100 | | --Dcom.sun.management.jmxremote.local.only=false |
101 | | --Dcom.sun.management.jmxremote.authenticate=false |
102 | | --Dcom.sun.management.jmxremote.ssl=false |
103 | | --Xms256m |
104 | | --Xmn512m |
105 | | --Xmx4g |
106 | | --XX:MaxMetaspaceSize=256m |
107 | | --XX:ParallelGCThreads=8 |
108 | | --XX:ConcGCThreads=4 |
109 | | -su.interference.standalone.Start |
110 | | -``` |
0 commit comments