bea.com | products | dev2dev | support | askBEA |
![]() |
![]() |
|
![]() |
e-docs > WebLogic Platform > WebLogic Integration > Starting, Stopping, and Customizing > WebLogic Integration Commands |
Starting, Stopping, and Customizing
|
WebLogic Integration Commands
This section provides system administrators and developers with information about key WebLogic Integration commands. It is organized into the following topics:
Command List
The following table provides the name and a brief description of each command documented in this section.
Environment Variables
The following table provides the name and a brief description of each environment variable referenced by a WebLogic Integration command.
Note: The italicized string DOMAIN_NAME is used as a placeholder for a pathname in this document. Specifically, it represents the full pathname for the root of this domain. Unlike other terms shown in italic monospace font (such as WLI_HOME), DOMAIN_HOME is not an environment variable.
Command Descriptions
This section presents descriptions of the WebLogic Integration commands, arranged in alphabetical order. The following figure summarizes the format of each command description.
Figure B-1 Command Description Format
bulkimporter
Name
bulkimporter—import workflow objects from Java Archive (JAR) files
Synopsis
bulkimporter -user bpm_user -password bpm_password -url
wls_server_url -orgid org_name {-file file_name |-dir
full_dir_path | -dir full_dir_path -file file_name}
[-activate] [-packagepwd password] [-help] [-quiet]
Description
The bulkimporter command allows you to import workflow packages from the command line without using the WebLogic Integration Studio. A workflow package contains the following workflow objects:
Organizations, users, and roles cannot be imported.
At least one jar file must be specified on the command line but many jar files can be imported in one command as shown in the following supported combinations:
If the -quiet option is not specified, then a listing of all the objects imported into WebLogic Integration are displayed.
You can also import workflow objects using the WebLogic Integration Studio. For more information, see "Importing and Exporting Workflow Packages" in Using the WebLogic Integration Studio.
Options
The following table summarizes the options for the bulkimporter command.
UNIX Files Windows Files Environment This command references the following environment variables: If WLI_HOME is not set, this command executes the setenv command.
$WLI_HOME/bin/bulkimporter
%WLI_HOME%\bin\bulkimporter.cmd
WL_HOME
WLI_HOME
JAVA_HOME
bulkloader
Name
bulkloader—import, export, or delete repository data
Synopsis
bulkloader [-wlibc] cfg_file
bulkloader -load [-txAll] [-initDB][-wlibc] data_file
Description
The bulkloader command allows you to import, export, or delete B2B configuration data from the repository. The content of cfg_file specifies the action to be taken, provides database access information, and, if required for the action, supplies the name of the XML file to be used to update the repository.
If the -load option is used, the file specified (data_file) is the XML file to be imported to the repository. The database information is obtained from settings in the setDBVars command for the current domain. The current domain is set by the setdomain command. You can verify the current domain with the checkdomain command.
For detailed information about the Bulk Loader, and the contents of the cfg_file and data_file files, see Working with the Bulk Loader in Administering B2B Integration.
Note: By default, the Bulk Loader does not import, export, or delete data while the B2B engine is running. If, for some reason, the B2B engine does not shut down normally, the Bulk Loader fails with the following error:
ERROR: WLC is still running or was shut down abnormally.
To override this error and force the command to execute by modifying the Bulk Loader command file, see "Forcing the Bulkloader" in Working with the Bulk Loader in Administering B2B Integration.
Options
The following table summarizes the options for the bulkloader command.
UNIX Files Windows Files Environment This command references the following environment variables: When executed with the -load option, this command references: If WLI_HOME is not set, this command executes the setenv command.
$WLI_HOME/bulkloader
$WLI_HOME/bin/setdbdata
$WLI_HOME/setenv.sh%WLI_HOME%\bin\bulkloader.cmd
%WLI_HOME%\bin\setdbdata.cmd
%WLI_HOME%\setEnv.cmdDB_JVMARGS
JAVA_HOME
WLI_HOME
WLICPDB_DRIVER
DB_URL
DB_USER
DB_PASSWORD
bulkmigrator
Name
bulkmigrator—migrate a repository data file
Synopsis
bulkmigrator collaborate1.0_file wlintegration2.0_file
Description
The bulkmigrator command converts an XML data file exported from WebLogic Collaborate 1.0.x (collaborate1.0_file) to the format required for WebLogic Integration 2.0 (wlintegration2.0_file). Some additional steps must be taken to make the file compatible for import to WebLogic Integration 7.0.
For detailed instructions, see "Migrating from Releases Prior to WebLogic Integration 2.1" in Introduction to Migration in BEA WebLogic Integration Migration Guide.
Options
None.
UNIX Files
$WLI_HOME/bin/bulkmigrator
Windows Files
%WLI_HOME%\bin\bulkmigrator.cmd
Environment
This command references the following environment variables:
JAVA_HOME
JAVACLASSPATH
checkdomain
Name
checkdomain—validate a domain and set WLI_DOMAIN for the calling process
Synopsis
checkdomain
Description
The checkdomain command is used in conjunction with setdomain and other command scripts. The checkdomain command validates that a domain has the directories and files required for other commands to run, and, if the domain is valid, it executes the domainname command to set WLI_DOMAIN for the calling process.
Note: The domainname command is created when the setdomain command is executed. This command stores the current WLI_DOMAIN setting.
Options
None.
UNIX Files
$WLI_HOME/bin/checkdomain
DOMAIN_HOME/checkdomain
$WLI_HOME/bin/domainname
$WLI_HOME/setenv.sh
Windows Files
%WLI_HOME%\bin\checkdomain.cmd
DOMAIN_HOME\checkdomain.cmd
%WLI_HOME%\bin\domainname.cmd
%WLI_HOME%\setEnv.cmd
Environment
This command sets WLI_DOMAIN and references WLI_HOME.
If WLI_HOME is not set, this command executes the setenv command.
createdb
Name
createdb—create repository tables and load system data
Synopsis
createdb [-f] [-noinit]
Description
The createdb command creates the WebLogic Integration repository tables in the database configured for the current domain, and then, if required, loads the system data into that database. The command calls the setdbdata command to load the current database access information and the bulkloader command to load the data.
The tables created are dependent on the requirements of the current domain. (For a description of the required tables, see Table 1-3 in Domain Configuration Requirements.) For example, if the current domain does not support B2B functionality, then the B2B tables are not created, and the B2B system data is not loaded. If the current domain is the WebLogic Integration samples domain, additional, sample-specific tables are created.
Note: Because the osql client used to create tables in a Microsoft SQL database is not available on UNIX, you cannot use the createdb command to create tables in a Microsoft SQL database from a UNIX system.
Options
The following table summarizes the options for the createdb command.
UNIX Files Windows Files Environment The createdb command references the following environment variables: If WLI_HOME is not set, this command executes the setenv command.
$WLI_HOME/bin/createdb
$WLI_HOME/bin/setdbdata
$WLI_HOME/bin/bulkloader
$WLI_HOME/dbscripts/$DB_TYPE/REPOSITORY_SCHEMA_BASE.sql
$WLI_HOME/dbscripts/$DB_TYPE/REPOSITORY_SCHEMA.sql
$WLI_HOME/dbscripts/$DB_TYPE/PERSISTENCE_SCHEMA.sql
$WLI_HOME/dbscripts/$DB_TYPE/BPM_SCHEMA.sql
$SAMPLES_HOME/integration/samples/wlis/dbscripts/$DB_TYPE/WLIS_SCHEMA.sql
$SAMPLES_HOME/integration/samples/e2e/dbscripts/$DB_TYPE/E2E_SCHEMA.sql
$WLI_HOME/adapters/dbms/src/sql/msql/cust.sql
$WLI_HOME/adapters/dbms/src/sql/msql/evnt.sql
$WLI_HOME/adapters/dbms/src/sql/oracle/cust.sql
$WLI_HOME/adapters/dbms/src/sql/oracle/evnt.sql
$WLI_HOME/adapters/dbms/src/sql/pointbase/cust.sql
$WLI_HOME/adapters/dbms/src/sql/pointbase/evnt.sql
$WLI_HOME/adapters/dbms/src/sql/sybase/cust.sql
$WLI_HOME/adapters/dbms/src/sql/sybase/evnt.sql
$WLI_HOME/dbscripts/SystemRepData.xml
$WLI_HOME/setenv.sh%WLI_HOME%\bin\createDB.cmd
%WLI_HOME%\bin\setdbdata.cmd
%WLI_HOME%\bin\bulkloader.cmd
%WLI_HOME%\dbscripts\%DB_TYPE%\REPOSITORY_SCHEMA_BASE.sql
%WLI_HOME%\dbscripts\%DB_TYPE%\REPOSITORY_SCHEMA.sql
%WLI_HOME%\dbscripts\%DB_TYPE%\PERSISTENCE_SCHEMA.sql
%WLI_HOME%\dbscripts\%DB_TYPE%\BPM_SCHEMA.sql
%SAMPLES_HOME%\integration\samples\wlis\dbscripts\%DB_TYPE%\WLIS_SCHEMA.sql
%SAMPLES_HOME%\integration\samples\e2e\dbscripts\%DB_TYPE%\E2E_SCHEMA.sql
%WLI_HOME%\adapters\dbms\src\sql\msql\cust.sql
%WLI_HOME%\adapters\dbms\src\sql\msql\evnt.sql
%WLI_HOME%\adapters\dbms\src\sql\oracle\cust.sql
%WLI_HOME%\adapters\dbms\src\sql\oracle\evnt.sql
%WLI_HOME%\adapters\dbms\src\sql\pointbase\cust.sql
%WLI_HOME%\adapters\dbms\src\sql\pointbase\evnt.sql
%WLI_HOME%\adapters\dbms\src\sql\sybase\cust.sql
%WLI_HOME%\adapters\dbms\src\sql\sybase\evnt.sql
%WLI_HOME%\dbscripts\SystemRepData.xml\
%WLI_HOME%\setEnv.cmdCLCP
DB_COMMAND
DB_CREATE
DB_JVMARGS
DB_PORT
DB_SCRIPT_DIR
DB_TYPE
JAVA_HOME
POINTBASE_HOME
SAMPLES_HOME
WLI_DOMAIN
WLI_HOME
createmssql
createsybase
Name
createmssql—create Microsoft SQL database and execute a script in that database
createsybase—create Sybase database and execute a script in that database
Synopsis
createmssql database_name sql_script
createsybase database_name sql_script
Description
The createmssql and createsybase commands check for the existence of the specified database. If the database exists, the command then runs the specified SQL script. (This action is equivalent to invoking the DB_COMMAND environment variable, which also executes the specified sql_script.) If the database does not exist, it is created, and the specified script is executed in the newly created database.
For example, if a Microsoft SQL database named WLIDB is configured for the current domain, the DB_CREATE environment variable in the %WLI_DOMAIN%\dbInfo\mssql\setDBVars command file is set as follows:
DB_CREATE=call %WLI_HOME%\dbscripts\mssql\createmssql WLIDB
The DB_CREATE environment variable is invoked by the createdb command as follows:
%DB_CREATE%REPOSITORY_SCHEMA_BASE.sql
If the WLIDB database already exists, invoking the DB_CREATE environment variable is equivalent to invoking the DB_COMMAND environment variable. If the WLIDB database does not exist, it is created, and the specified script is executed in that database.
Note: Because the osql client is not available on UNIX, the createmssql command is not available on UNIX. You cannot use the createdb command on a UNIX system to create tables in a Microsoft SQL database.
Options
None.
UNIX Files
$WLI_HOME/dbscripts/sybase/createsybase
Windows Files
%WLI_HOME%\dbscripts\mssql\createmssql.cmd
%WLI_HOME%\dbscripts\sybase\createsybase.cmd
Environment
These commands reference the following environment variables:
SQLARGS
DB_COMMAND
domainname
Name
domainname—set or verify the current domain set by the setdomain command
Synopsis
domainname
Description
This machine-generated command stores the current domain setting. This file is generated when the setdomain command is executed. The checkdomain command uses the setting in this file to verify the domain and set WLI_DOMAIN for the calling process.
Options
None.
UNIX Files
$WLI_HOME/bin/domainname
Windows Files
%WLI_HOME%\bin\domainname.cmd
Environment
This command sets the WLI_DOMAIN environment variable.
fb
Name
fb—start Format Builder
Synopsis
fb
Description
This command starts the Format Builder client. A shortcut to the fb.cmd command is provided on the Windows Start menu.
Options
None.
UNIX Files
$WLI_HOME/bin/fb
$WLI_HOME/setenv.sh
Windows Files
%WLI_HOME%\bin\fb.cmd
%WLI_HOME%\setEnv.cmd
Environment
The fb command sets but does not export the CP environment variable:
The fb command references the following environment variables:
WLICP
WLI_HOME
JAVA_HOME
If WLI_HOME is not set, this command executes the setenv command.
launchSamplesPage
Name
launchSamplesPage—open the samples launcher page in the default Web browser
Synopsis
launchSamplesPage
Description
This command opens http://localhost:7001/index.html. If the administration server for the samples domain is running on the local machine, this command opens a page from which the samples can be run.
Note: On UNIX systems, the browser executable netscape must be included in the system path variable.
Options
None.
UNIX Files
$SAMPLES_HOME/integration/samples/bin/launchSamplesPage
Windows Files
%SAMPLES_HOME%\integration\samples\bin\launchSamplesPage.cmd
Environment
No environment variables are referenced or set.
mdbgenerator
Name
mdbgenerator—generate a deployable JAR file to listen on a custom queue
Synopsis
mdbgenerator -queue queue_name [-min number] [-max number]
[-order number] [-transact] [-validate] [-timeout seconds] [-help]
Description
The message driven bean (MDB) generator utility (the mdbgenerator command) generates a deployable Java Archive (JAR) file that can be used to listen on a custom Java Message Service (JMS) queue.
Options
The following table summarizes the options for the mdbgenerator command.
UNIX Files Windows Files Environment This command references the following environment variables: If WLI_HOME is not set, this command executes the setenv command.
$WLI_HOME/bin/mdbgenerator
$WLI_HOME/setenv.sh%WLI_HOME%\bin\mdbgenerator
%WLI_HOME%\setEnv.cmdWLI_HOME
WL_HOME
JAVA_HOME
migratedb
Name
migratedb—migrate a database from WebLogic Integration 2.1 or WebLogic Integration 2.1 Service Pack 1 (SP1) to WebLogic Integration 7.0
Synopsis
migratedb
Description
The migratedb command creates the scripts required to migrate the database configured for the current domain, and then executes those scripts against the database. The command updates WebLogic Integration 2.1 or WebLogic Integration 2.1 SP1 database tables and schema as required for compatibility with WebLogic Integration 7.0.
For additional information see BEA WebLogic Integration Migration Guide.
Options
None.
UNIX Files
$WLI_HOME/bin/migratedb
$WLI_HOME/bin/checkdomain
$WLI_HOME/bin/setdbdata
$WLI_HOME/bin/bulkloader
$WLI_HOME/setenv.sh
$WLI_HOME%/dbscripts/migrate/SystemRepData.xml
Windows Files
%WLI_HOME%\bin\migratedb.cmd
%WLI_HOME%\bin\checkdomain.cmd
%WLI_HOME%\bin\setdbdata.cmd
%WLI_HOME%\bin\bulkloader.cmd
%WLI_HOME%\setEnv.cmd
%WLI_HOME%\dbscripts\migrate\SystemRepData.xml
Environment
This command references the following environment variables:
DB_DRIVER
DB_NAME
DB_PASSWORD
DB_SERVERNAME
DB_TYPE
DB_URL
DB_USER
JAVA_HOME
WLI_DOMAIN
WLI_HOME
WLICP
If WLI_HOME is not set, this command executes the setenv command.
PIMigrator
Name
PIMigrator—migrate a workflow template
Synopsis
PIMigrator InputTemplate.xml OutputTemplate.xml
Description
The PIMigrator command updates a template created for use with Collaborate 1.0 to the format required by WebLogic Integration 2.0/2.1.
Options
None.
UNIX Files
$WLI_HOME/bin/PIMigrator
$WLI_HOME/lib/dtd/PITemplateMigration.xsl
Windows Files
%WLI_HOME%\bin\PIMigrator.cmd
%WLI_HOME%\lib\dtd\PITemplateMigration.xsl
Environment
This command references the following environment variables:
JAVA
WLC_HOME
WLICP
RunSamples
Name
RunSamples—configure the samples database and start WebLogic Server in the samples domain
Synopsis
RunSamples [option . . . ]
Description
The RunSamples command performs the following tasks for the samples domain:
When the RunSamples command is executed with the default option, all, or with no options, its behavior depends on whether it is being run for the first time against the database configured for the samples domain. For additional information see Configuring and Starting the Samples Domain.
Options
The following table summarizes the options for the RunSamples command.
UNIX Files Windows Files Environment This command references the following environment variables: If WLI_HOME is not set, this command executes the setenv command.
$SAMPLES_HOME/integration/samples/bin/RunSamples
$WLI_HOME/bin/setdomain
$SAMPLES_HOME/integration/samples/bin/SetSampleData%SAMPLES_HOME%\integration\samples\bin\RunSamples.cmd
%WLI_HOME%\bin\setdomain.cmd
%SAMPLES_HOME%\integration\samples\bin\SetSampleData.cmdWLI_HOME
WLICP
WL_HOME
JAVA_HOME
DB_TYPE
setdbdata
Name
setdbdata—load the database-specific variables into the current process
Synopsis
setdbdata
Description
The setdbdata command loads the database-specific variables into the current process by:
Options
None.
UNIX Files
$WLI_HOME/bin/setdbdata
$WLI_HOME/bin/checkdomain
DOMAIN_HOME/setdbdata
DOMAIN_HOME/checkdomain
DOMAIN_HOME/dbInfo/$DB_TYPE/setDBVars
DOMAIN_HOME/dbInfo/$DB_TYPE/setDBVarsExt
DOMAIN_HOME/dbInfo/setdbtype
Windows Files
%WLI_HOME%\bin\setdbdata.cmd
%WLI_HOME%\bin\checkdomain.cmd
DOMAIN_HOME\setdbdata.cmd
DOMAIN_HOMEn\checkdomain.cmd
DOMAIN_HOME\dbInfo\%DB_TYPE%\setDBVars
DOMAIN_HOME\dbInfo\%DB_TYPE%\setDBVarsExt
DOMAIN_HOME\dbInfo\setdbtype
Environment
In addition to the variables set by setdbtype and setDBVars, the setdbdata command sets the following:
DBINFO
DB_CREATE
DB_DIR
DB_PROPERTIES
Note: DB_CREATE is set to DB_COMMAND if it is not defined by setDBVars.
setdbtype
Name
setdbtype—set the database type for the domain
Synopsis
setdbtype
Description
This command is generated based on information provided when you use the Configuration Wizard to create a domain, execute the switchdb command, or use the WebLogic Integration Database Wizard (the wliconfig command) to update the database for a domain.
Options
None.
UNIX Files
DOMAIN_HOME/dbInfo/setdbtype
Windows Files
DOMAIN_HOME\dbInfo\setdbtype.cmd
Environment
This command sets the DB_TYPE environment variable.
setDBVars
setDBVarsExt
Name
setDBVars—set the basic database variables for the domain
setDBVarsExt—set the extended database variables for the domain
Synopsis
setDBVars
setDBVarsExt
Description
The setDBVars and setDBVarsExt commands for a domain are updated based on the information provided when you use the Configuration Wizard to create a domain, execute the switchdb command, or use the WebLogic Integration Database Wizard (the wliconfig command) to update the database for a domain.
Options
None.
UNIX Files
$WLI_DOMAIN/dbInfo/$DB_TYPE/setDBVars
$WLI_DOMAIN/dbInfo/$DB_TYPE/setDBVarsExt
Windows Files
%WLI_DOMAIN%\dbInfo\%DB_TYPE%\setDBVars
%WLI_DOMAIN%\dbInfo\%DB_TYPE%\setDBVarsExt
Environment
The setDBVars command sets the following environment variables:
DB_JVMARGS
DB_USER
DB_PASSWORD
DB_CODESET
DB_SERVERNAME
DB_NAME
DB_URL
DB_DRIVER
DB_SCRIPT_DIR
SQLARGS
DB_COMMAND
DB_CREATE
CLCP
The setDBVarsExt command sets the following environment variables:
DB_CATALOG
DB_SCHEMA
DB_PINGTABLE
Note: Some variables are specific to database type. For example, CLCP is set for PointBase only.
setdomain
Name
setdomain—set the current domain
Synopsis
setdomain domain_path
Here, domain_path is the path to the domain relative to the current directory. For example, if are on a UNIX system, and execute the command from the $BEA_HOME directory to set the current domain to $BEA_HOME/user_projects/mydomain, enter the following:
setdomain user_projects/mydomain
If you execute the command from the domain directory (for example, from the $BEA_HOME/user_projects/mydomain directory), you need not specify domain_path.
Note: You can execute the setdomain command from any directory if you first execute the setenv command.
Description
The setdomain command verifies that the specified directory is a valid domain. If the domain is valid, the command sets the WLI_DOMAIN environment variable to the specified domain and creates the domainname command to store the setting. The current domain must be set for the checkdomain, setdbdata, RunSamples, and switchdb commands.
Options
None.
UNIX Files
$WLI_HOME/bin/setdomain
$WLI_HOME/setenv.sh
$WLI_HOME/bin/domainname
Windows Files
%WLI_HOME%\bin\setdomain.cmd
%WLI_HOME%\setEnv.cmd
%WLI_HOME%\bin\domainname.cmd
Environment
The setdomain command sets the WLI_DOMAIN environment variable and references the WLI_HOME environment variable.
If WLI_HOME is not set, this command executes the setenv command.
setenv
Name
setenv—set common WebLogic Integration environment variables
Synopsis
setenv
Description
The setenv command sets the basic WebLogic Integration environment settings.
Options
None.
UNIX Files
$WLI_HOME/setenv.sh
$WLI_HOME/bin/setenv
Windows Files
%WLI_HOME%\setEnv.cmd
%WLI_HOME%\bin\setenv.cmd
%WLI_HOME%\samples\bpm_api\commandline\setEnv.cmd
%WLI_HOME%\samples\bpm_api\plugin\setEnv.cmd
Environment
The setenv command sets the following environment variables:
BEA_HOME
JAVA_HOME
SAMPLES_HOME
WL_HOME
WLI_HOME
WLICOMMONCP
WLICP
WLISERVERCP
The command also adds %JAVA_HOME%\bin to the existing PATH environment variable.
SetDomainTypeData
SetSampleData
Name
SetDomainTypeData—set environment variables for the DomainType domain
SetSampleData—set environment variables for the samples domain
Synopsis
SetDomainTypeData
SetSampleData
Description
The SetDomainTypeData command sets environment variables for a custom domain created with the Configuration Wizard.
Here the value of DomainType is determined by which Configuration Wizard template is used to create the custom domain. For example, if you used the WebLogic Integration template, the command is SetWliDomainData.
The SetSampleData command sets environment variables for the WebLogic Integration samples domain.
Options
None.
UNIX Files
DOMAIN_HOME/SetDomainTypeData
$SAMPLES_HOME/integration/samples/bin/SetSampleData
$WLI_HOME/setenv.sh
$WLI_HOME/bin/setdbdata
Windows Files
DOMAIN_HOME\SetDomainTypeData
%SAMPLES_HOME%\integration\samples\bin\SetSampleData.cmd
%WLI_HOME%\setEnv.cmd
%WLI_HOME%\setdbdata.cmd
Environment
Two commands, SetDomainTypeData and SetSampleData set the following environment variables for the custom domain and the WebLogic Integration sample domain, respectively.
WLI_SAMPLES_HOME (SetSampleData)
WLI_DOMAIN_HOME (SetDomainTypeData)
WLIS_HOST_AND_PORT
WLIS_USER_NAME
WLIS_PASSWORD
JDBC_DATASOURCE_JNDI_NAME
EVENTROUTER_URL
CMNCP
CP
SVRCP
The SetDomainTypeData command references the following environment variables:
WLICP
WLISERVERCP
WLI_HOME
CMNCP
SVRCP
WLI_DOMAIN_HOME
WLIS_HOST_AND_PORT
setupAppView
setupEDIAppView
Name
setupAppView—set up the application view for the sample adapter
setupEDIAppView—set up the application view for the EDI adapter
Synopsis
setupAppView
setupEDIAppView
Description
The setupAppView command sets up the application view for sample adapter (WLISAppView). The setupEDIAppView command sets up the application view for the EDI adapter (EDIAppView).
Both commands execute the SetSampleData command before issuing the java command that sets up the application view.
Options
None.
UNIX Files
$SAMPLES_HOME/integration/samples/bin/setupAppView
$SAMPLES_HOME/integration/samples/bin/setupEDIAppView
$SAMPLES_HOME/integration/samples/bin/SetSampleData
$WLI_HOME/setenv.sh
Windows Files
%SAMPLES_HOME%\integration\samples\bin\setupAppView.cmd
%SAMPLES_HOME%\integration\samples\bin\setupEDIAppView.cmd
%SAMPLES_HOME%\integration\samples\bin\SetSampleData.cmd
%WLI_HOME%\setEnv.cmd
Environment
The setupAppView and the setupEDIAppView commands reference the following environment variables:
CP
DB_JVMARGS
JAVA_HOME
WLI_HOME
WLIS_HOST_AND_PORT
WLIS_PASSWORD
WLIS_USER_NAME
In addition, the setupAppView command references the following environment variables:
DB_PINGTABLE
DB_CATALOG
DB_SCHEMA
EVENTROUTER_URL
JDBC_DATASOURCE_JNDI_NAME
showdomain
Name
showdomain—display the current domain
Synopsis
showdomain
Description
This command verifies that the current domain is valid, and it displays the current domain setting.
Options
None.
UNIX Files
$WLI_HOME/bin/showdomain
$WLI_HOME/bin/checkdomain
$WLI_HOME/setenv.sh
Windows Files
%WLI_HOME%\bin\showdomain.cmd
%WLI_HOME%\bin\checkdomain.cmd
%WLI_HOME%\setEnv.cmd
Environment
The showdomain command references the WLI_HOME environment variable.
If WLI_HOME is not set, this command executes the setenv command.
startAiconsole
startB2bconsole
Name
startAiconsole—start the Application View Console
startB2bconsole—start the B2B Console
Synopsis
startAiconsole
startB2bconsole
Description
The startAiconsole command launches your default browser and opens the URL for the Application View Console (http://localhost:7001/wlai). This command can only be used to access the Application View Console if the administration server for the domain is running on the local host.
The startB2bconsole command launches your default browser and opens the URL for the B2B Console (http://localhost:7001/b2bconsole). This command can only be used to access the B2B Console if the administration server for the domain is running on the local host.
Shortcuts to these commands are provided on the Windows Start menu.
Note: On UNIX systems, the browser executable netscape must be included in the system path variable.
Options
None.
UNIX Files
These command are not available on UNIX systems.
Windows Files
%WLI_HOME%\bin\startAiconsole.cmd
%WLI_HOME%\bin\startB2bconsole.cmd
Environment
This command references the $WLI_HOME environment variable.
startpointbasecommander
Name
startpointbasecommander—start the PointBase administrative tool
Synopsis
startpointbasecommander
Description
The startpointbasecommander command verifies the current database setting, and if the setting is PointBase, it launches PointBase commander, the PointBase administrative tool.
Options
None.
UNIX Files
$WLI_HOME/bin/startpointbasecommander
$WLI_HOME/bin/setdbdata
Windows Files
%WLI_HOME%\bin\startpointbasecommander.cmd
%WLI_HOME%\bin\setdbdata.cmd
Environment
This command references the following environment variables:
CLCP
DB_JVMARGS
DB_PORT
DB_TYPE
JAVA_HOME
POINTBASE_HOME
If WLI_HOME is not set, this command executes the setenv command.
startWeblogic
Name
startWeblogic—start WebLogic Server and deploy WebLogic Integration resources
Synopsis
startWeblogic
Description
The startWeblogic command:
Options
None.
UNIX Files
DOMAIN_HOME/startWeblogic
DOMAIN_HOME/SetDomainTypeData
DOMAIN_HOME/dbinfo/setdbdata
$SAMPLES_HOME/integration/samples/bin/SetSampleData
$WLI_HOME/setenv.sh
Windows Files
DOMAIN_HOME\startWeblogic.cmd
DOMAIN_HOME\SetDomainTypeData.cmd
DOMAIN_HOME\dbInfo\setdbdata.cmd
%SAMPLES_HOME%\integration\samples\bin\SetSampleData.cmd
%WLI_HOME%\setEnv.cmd
Environment
The startWeblogic command references the following environment variables:
CLCP
DB_JVMARGS
DB_PORT
DB_TYPE
JAVA_HOME
SVRCP
WL_HOME
WLI_DOMAIN_HOME
WLI_HOME
stopWeblogic
Name
stopWeblogic—shut down WebLogic Server
Synopsis
stopWeblogic
Description
The stopWeblogic command executes the setenv command, and then issues a shutdown request to the WebLogic Server running in the domain.
Options
None.
UNIX Files
DOMAIN_HOME/stopWeblogic
$WLI_HOME/setenv.sh
Windows Files
DOMAIN_HOME\stopWeblogic.cmd
%WLI_HOME%\setEnv.cmd
Environment
The stopWeblogic command references the following environment variables:
BEA_HOME
DB_JVMARGS
JAVA_HOME
WL_HOME
WLI_HOME
WLISERVERCP
studio
Name
studio—start the WebLogic Integration Studio
Synopsis
studio
Description
The studio command starts the WebLogic Integration Studio client.
Options
None.
UNIX Files
$WLI_HOME/bin/studio
$WLI_HOME/setenv.sh
Windows Files
%WLI_HOME%\bin\studio.cmd
%WLI_HOME%\setEnv.cmd
Environment
The studio command sets CP=$WLI_HOME/lib/wlpi-studio.jar:$WLICP (UNIX) or CP=%WLI_HOME%\lib\wlpi-studio.jar:%WLICP% (Windows), and references the following environment variables:
CP
JAVA_HOME
WLI_HOME
WLICP
If WLI_HOME is not set, this command executes the setenv command.
switchdb
Name
switchdb—update the database configured for the current domain
Synopsis
switchdb mssql|oracle|pointbase|sybase
Description
The switchdb command updates the database configuration for the current domain by:
The switchdb command does not update the setDBVars file. If the database configuration reflected in the setDBVars file requires modification, use the WebLogic Integration Database Wizard (the wliconfig command) to update the configuration.
Options
None.
UNIX Files
$WLI_HOME/bin/switchdb
$WLI_HOME/bin/checkdomain
$WLI_HOME/setenv.sh
$WLI_DOMAIN/dbInfo/setdbtype
$WLI_DOMAIN/dbInfo/$DB_TYPE/setDBVars
$WLI_DOMAIN/scripts/SwitchDB.xml
$WLI_HOME/lib/scripts/SwitchDB.xml
Windows Files
%WLI_HOME%\bin\switchdb.cmd
%WLI_HOME%\bin\checkdomain.cmd
%WLI_HOME%\setEnv.cmd
%WLI_DOMAIN%\dbInfo\setdbtype.cmd
%WLI_DOMAIN%\dbInfo\%DB_TYPE%\setDBVars.cmd
%WLI_DOMAIN%\scripts\SwitchDB.xml
%WLI_HOME%\lib\scripts\SwitchDB.xml
Environment
The switchdb command sets the DBINFO and DB_TYPE environment variables, and references the WLI_DOMAIN and JAVA_HOME environment variables.
If WLI_HOME is not set, this command executes the setenv command.
worklist
Name
worklist—start the WebLogic Integration Worklist
Synopsis
worklist
Description
The worklist command starts the WebLogic Integration Worklist client.
Options
None.
UNIX Files
$WLI_HOME/bin/worklist
$WLI_HOME/setenv.sh
Windows Files
%WLI_HOME%\bin\worklist.cmd
%WLI_HOME%\setEnv.cmd
Environment
The worklist command sets CP=$WLI_HOME/lib/wlpi-worklist.jar:$WLICP (UNIX) or CP=%WLI_HOME%\lib\wlpi-worklist.jar:%WLICP% (Windows), and references the following environment variables:
CP
JAVA_HOME
WLI_HOME
WLICP
If WLI_HOME is not set, this command executes the setenv command.
wliconfig
Name
wliconfig—launch the WebLogic Integration Database Wizard
Synopsis
wliconfig
Description
This command launches the WebLogic Integration Database Wizard. For additional information, see Using the Database Wizard.
Options
No options are currently supported. The wizard prompts for the required information.
UNIX Files
DOMAIN_HOME/wliconfig
$WLI_HOME/setenv.sh
Windows Files
DOMAIN_HOME\wliconfig.cmd
%WLI_HOME%\setEnv.cmd
Environment
The wliconfig command references the following environment variables:
$JAVA_HOME
$WLI_HOME
If WLI_HOME is not set, this command executes the setenv command.
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |