Create an instance (create)
- Last Updated: March 11, 2026
- 3 minute read
- OpenEdge
- Version 13.0
- Documentation
Purpose
Create a new instance of PAS for OpenEdge by running from /bin directory of the PAS for OpenEdge installation (
$CATALINA_HOME/bin/tcman.sh create) or using
pasman create.
Syntax
|
Parameters
- general_options
- Specify one or more of the general TCMAN options. Run
tcman.sh help createto see which general options are appropriate. - –f
- Copy all deployed web application archives (.war files) from $CATALINA_HOME to the new instance.
- –x
- Bypasses port availability validation during instance
creation, allowing you to reuse explicitly specified ports that are already
in use. Use this option only for controlled scenarios such as migrations or
instance replacement; default port checking behavior remains unchanged.Note: PAS for OpenEdge validates port availability during instance creation to prevent accidental conflicts, misconfiguration, and startup failures. The
-xoption is intended for advanced scenarios where administrators intentionally reuse ports as part of a controlled migration or replacement process. - –p port_num
- Specify the TCP port that listens for HTTP messages. The default is 8080.
- –P port_num
- Specify the TCP port that listens for HTTPS messages. The default is 8443.
- –s port_num
- Specify the TCP port to use to stop an instance. On Windows systems, you must specify a shutdown port. On Linux, shutdown ports are optional.
- –j port_num
- Specify the TCP port that listens for AJP13 messages (an Apache protocol for handling requests from a web server to an application server). The default is 8009.
- -m uid:pwd
- Specify a user name and password that will be required to
access Tomcat container-level security, which includes the manager and oemanager web applications. Replaces the defaults (
tomcat:tomcat) in /conf/tomcat-users.xml. - –N instance_alias
- Specify an alias for the instance. If you do not specify an alias, the
instance name will be the name of the directory where the instance is
created.Note: All instances are automatically registered for tracking when they are created. However, for tracking to function, the instance name must not contain spaces or any of the following characters:
"[ . # | ] $ ? + = { / , }" - –U user_id
- Specify the user-id of the owner of all the files and
directories of the instance. The default is the user-id of the current
process.
–Gmust be specified if you use this option. - –G group_id
- Specify the group-id of the owner of all the files and
directories of the instance. The default is the group-id of the current
process.
–Umust be specified if you use this option.
- -Z {dev | prod | pas}
- Specify the initial configuration of an instance:
dev—Creates an instance with enabled transports and a ROOT web application intended for use with a development license implementing no security features.prod—Creates an instance with disabled transports and a ROOT web application as the first step in securing an instance for use with a production license.pas—Creates an instance and replaces the required ROOT.war file with a custom ROOT.war file containing a web application that responds to any request with a400 "bad request". This replacement secures the ROOT web application and serves as a blank canvas for your ABL applications. Before starting the instance, you must deploy an ABL application.For more information about the replacement ROOT.war file, see the noaccess.README file included in the $CATALINA_HOME/extras/noaccess.war file.
Note: Instances created with thedevoption are not intended for use in production. Instances created usingprodandpasoptions require additional configuration to create a secure production server. - base_path
- Specify the path name where you will create the instance.
- abl-app-name
- Optional abl application name.
Example
To create an development instance acme3 in the acme directory:
|