Developing Apama Applications > Using Apama Studio > Launching Projects > Running Apama projects > Adding a correlator > Correlator arguments
Correlator arguments
The Correlator Arguments tab specifies the options and arguments that Apama Studio uses to start the correlator.
You can accept the default values or change one or more arguments. You can also add arguments. In addition, you can also control the behavior with the following options:
*Hostname — localhost. The name of the correlator host machine.
*Port . This is the port on which the correlator listens for monitoring and management requests.
*Log level. Default is INFO.
*Log to file. Default is ${LAUNCH_CONFIG_NAME}_${CORRELATOR_NAME}.output.log.
*Replay log. Default is Correlator_1_${START_TIME}_${ID}.replay.log.
*Replay log mode. Accept replay default or select input. See Using a replay log to diagnose problems.
*Reuse Correlator — Select this option to use an already running correlator.
*Clear Correlator — Select this option to delete all the correlator contents when the launch starts.
*Java Support — Select this option to provide support Java support for Apama Java applications. Normally this is automatically selected when an Apama Java application is created in Apama Studio.
*JMS Support — Select this option to provide JMS support for Correlator-integrated JMS messaging. Normally this is automatically selected when the JMS Correlator-Integrated Adapter is added to an Apama application.
*Distributed MemoryStore Support — Select this option to provide support for distributed MemoryStore. With the distributed MemoryStore, you can create distributed stores that provide access to data that will be shared among Apama applications running in separate correlators.
*Maximum java heap size in Mb (-Xmx). Default is 512.
*Maximum java off-heap storage in Mb (-XX:MaxDirectMemorySize). Default is 16384.
*Extra command line arguments. Specify any additional arguments for starting the correlator. See Starting the event correlator.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.