This functionality is only available for certain module packages.

You are here: Administration > Runtime options > Java Virtual Machine Arguments (VMArgs) > org.foederal.sn.connectionURL

org.foederal.sn.connectionURL

The EEC argument must be transferred with the following syntax:

-D<Argument>=<Value>

EEC argument

Usage

-Dorg.foederal.sn.connectionURL=<Connection URL>

Optional

Annotation

The connection URL indicates the connection path to the data back end.

This can be a connection path to a database, an absolute path to an EOX file or a statement for a EOX file selection. As an exception an empty model that only includes the system library can also be specified.

EEC start with an empty model (only with system libraries:)

-Dorg.foederal.sn.connectionURL=proxy://empty
	

Selection of an EOX file on EEC Start (default setting):

The connection path is specified according to the following syntax:

-Dorg.foederal.sn.connectionURL=proxy://any
	

On start a file selection dialog for an EOX file appears. The dialog offers an option to select, whether access to the EOX file should be read-only. Any changes have to be exported as reusable library or as EOX file, if they should not be lost. If the option is deselected, the previous model will be changed. Any changes are stored in the selected EOX file.

EOX files:

The connection path to an EOX file for data back end is specified with the following syntax:

-Dorg.foederal.sn.connectionURL=eox:///<absoluter Pfad zur EOX-Datei>?mode=rw
		
	
Statement Meaning
<Drive letter:> Any drive letter, e.g. D:
<?> Initiates further options
<mode=rw> Defines the access rights. Possible values are:
  • r = read-only
  • rw = lead und write
<&> Initiates more options
<validate=true> Defines whether the model should be validated while opening. Possible values are:
  • true = validate model
  • false = no model validation

Example:

-Dorg.foederal.sn.connectionURL=eox:///C:/Users/Public/EPLAN/EngineeringConfiguration/<EEC installation folder>/eox/model.eox?mode=rw
	

Databases:

The structure of the connection path to a database depends on the specifications of the database vendor. The following explains the connection paths for the DBMS used

FastObjects

Connection path: fastobjects://<host[:port]>/<database>

<host> is the IP address or name of the database server. The value LOCAL allows for the database to be integrated into the EEC process (cf. Stand-Alone installation).

[:port] is the port number if the default ports (6001, 6002) are already in use.

<database> is the name of the database. In the case of the Stand-Alone installation, the path to the database must be stated, e.g., the folder db.

Examples:

-Dorg.foederal.sn.connectionURL=fastobjects://10.1.15.231/EECDB
-Dorg.foederal.sn.connectionURL=fastobjects://dbserver/EECDB
-Dorg.foederal.sn.connectionURL=fastobjects://LOCAL/db
-Dorg.foederal.sn.connectionURL=fastobjects://dbservername:10101/db

In the example below, in the configuration file ptserver.cfg, in the folder dbserver\fastobjects\installFiles, the entry [servers\ptserver] must be added as follows (for example, for port 10101):

[servers\ptserver]
# Activate server output
verboseMode=2
# define server port
service=10101

In EEC itself, the port must be stated in the .ini files at the connectionURL via a colon behind the server name:

-Dorg.foederal.sn.connectionURL=fastobjects://dbservername:10101/db