![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Table 41 lists the predefined properties you can use in the properties file. You can also add application-defined properties to this file. See Two Types of Properties.
All properties starting with ntservice are available only under Microsoft Windows. All other properties are platform independent.
Table 41 Wrapper Settable Properties Required on MS Windows Name of this service in the SCM service database. Required on MS Windows Name displayed to users of the Control Panel Services Applet for this service. Required on MS Windows Absolute path to the wrapper binary itself. Required when started as a service. Installing the service and then moving the binary is not recommended.Note that the back slash path separator must be escaped with addition back slash (or you can simply use the forward slash). A comma-separated list of dependent services that must be started before starting this service. Defaults to automatic if not set. true or false Defaults to true if not set.Must be false to use a specific account and password. Specifying true and specifying an account and password is considered illegal by the SCM. Be certain that the network domain is specified as part of the account. Otherwise, the SCM will reject the account as invalid when attempting to install the service. Password for the specified account. You can use a password that has been encrypted. In that case, prefix it with #! (pound exclamation mark). Used to specify a different directory than the current directory to launch the application. Useful when applications make use of relative paths. Arguments supplied to the application when it launches. The string is exactly as it would be typed on the command line, however, you must escape certain characters that terminate a Java property. Refer to standard Java property file syntax documentation for characters requiring escaping.To read a properties file that specifies SDK properties, include application.args=-system:propFile <SDK_Properties_file> .... The TIBCO Wrapper looks for the start() method on this class, which can also be specified directly via the java.start.method property. If the start() method is not supplied, then the standard Java static main() method is used. The TIBCO Wrapper attempts to invoke this static method on the start class. If the start() method is not supplied, then the standard Java static main() method is used. If this property is supplied, the utility will attempt to invoke this static method on the start class upon shutdown. any standard classpath Standard java classpath that will be passed along to the JVM without modification. Note that the TIBCO Wrapper only uses either tibco.class.path.extended or this property, but not both. If both are present, the utility takes tibco.class.path.extended instead of this property. Classpath that is expanded inline by the utility. Any directory is searched for .class, .jar, or .zip files and expands the final classpath to include all of these files for that directory. Any specific files in the classpath are passed along unaltered. The syntax is the same as for the extended property (-Xmx). For example, “32M”. The syntax is the same as for the extended property (-Xss). Allows setting of any Java properties to be passed along to the Java application. Takes the form of Java.property.foo=bar. There may be an unlimited number of these per properties file, within file system limitations. Allows setting of arbitrary extended JVM options (for example, -XServer -Xdebug). any env. variable value Overrides the environment variable is set. Otherwise, creates it and sets it for the application.Can be used to define any environment variable. For example defining tibco.env.PATH will override the existing PATH environment setting.See tibco.env Note below.The tibco.env.<varname> property allows you to override the PATH environment variable for C++ custom adapters running as a Windows Service.To support this, link the shared libraries that you want to be loaded through the overridden PATH with the MSVC /DELAYLOAD linker option. This allows the overridden PATH to take effect before the operating system attempts to load the dependent shared libraries.Adapters that use the TIBCO wrapper can use a separate SDK properties file. To do so, they specify the SDK properties file in the application.args property of the TIBCO Wrapper properties file as follows:
You can use separate properties files for SDK properties and TIBCO Wrapper properties for clarity. You can also place all properties into the wrapper properties file.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |