- After you set environment you can start SALOME. Go to the SALOME
- binaries directory (SalomePro-1.2d for the version 1.2d) by using
- of cd command and then type:
-
- salome --gui
-
- This will start SALOME servers and launch GUI desktop. If you want
- to launch SALOME in the batch mode, use --batch option:
-
- salome --batch
-
- If you want to launch SALOME using specific port, use --port key:
-
- salome --gui --port XXXX
-
- where XXXX is a port number.
- Note, that in this case you have to write the same port number into
- your ORB configuration file, which should be referenced by the
- $(OMNIORB_CONFIG) environment variable (usually it is an omniORB.cfg
- file), e.g.:
-
- ORBInitRef NameService=corbaname::<host-name>:<port-number>
-
- <host-name> is a name of host where Naming Service should be run
- and <port-number> is a number of port to be used.
- The default port number is 2809. The using of non-default port
- is useful when it is necessary for several users to launch
- SALOME on the same host.
-
- Use --help key to display additional information to learn other
- salome script options.
-
- Note: salome script is included into SALOME package only from 1.2d
- version. In order to run salome for the previous versions you should
- use runSalome script from the bin sub-directory of SALOME:
-
- cd bin
- runSalome
+ After you set environment you can start SALOME. Go to the KERNEL
+ module's binaries directory (KERNEL_2.2.0/bin/salome for the version
+ 2.2.0) by using of cd command and then type:
+
+ runSalome [<parameters>]
+
+ This will start SALOME according to the configuration parameters which
+ are described into salome.launch file, located in your home directory
+ ( $HOME/.salome_<version-number>/salome.launch ),
+ where <version_number> is number of SALOME version.
+
+ If this file does not exists, it is created on the first launch of
+ SALOME from <KERNEL_ROOT_DIR>/bin/salome/salome.launch.
+
+ You can modify SALOME launching options by editing
+ salome_<version_number>.launch file:
+
+ <Configuration-list>
+ <launchoptions>
+ <gui>yes</gui>
+ <logger>no</logger>
+ <xterm>no</xterm>
+ <portkill>yes</portkill>
+ <killall>no</killall>
+ </launchoptions>
+ <modules-list>
+ <module name="...">
+ <plugin name="..."/>
+ </module>
+ </modules-list>
+ <embedded-list>
+ <embeddedserver>...</embeddedserver>
+ </embedded-list>
+ <standalone-list>
+ <standaloneserver>...</standaloneserver>
+ </standalone-list>
+ </Configuration-list>
+
+ Each parameter described in salome.launch file can be overrided by
+ using corresponding keys for runSalome script:
+
+ --gui
+ Launch GUI desktop
+ --logger
+ Use logger server
+ --xterm
+ Start each server in its own xterm console window
+ --portkill
+ Kill SALOME, running on the current port
+ --killall
+ Kill SALOME, running on all ports
+ --modules=<module>,<module>,...,<module>
+ Use module(s), possible values are GEOM,SMESH,VISU,MED,SUPERV
+ --embedded=<container>,<container>,...<container>
+ Start specified container(s) embedded in SALOME Session server
+ (i.e. running in the same process), possible values are registry,
+ study, moduleCatalog, cppContainer, pyContainer, supervContainer
+ --standalone=<container>,<container>,...<container>
+ Start standalone container(s), possible values are registry,
+ study, moduleCatalog, cppContainer, pyContainer, supervContainer
+
+ Note that there is no key which corresponds to the <plugin> tag.
+ This tag can be used currently only for SMESH module to point external
+ meshers plugins which should be loaded by SMESH dynamically.
+ Refer <SMESH_ROOT_DIR>/doc/salome/tui/SMESH/PluginMeshers.html
+ for more information om meshers plugins.