You can specify the following installation options for the AdminApp object.
Use this option to change the backend ID during installation. This option is not available in an edit command.
Example usage:
Using Jacl:
Ensure each message-driven enterprise bean in your application or module is bound to a listener port name. Use this option to provide missing data or update a task.
Example usage:
Using Jacl:
$AdminApp install $ear {-BindJndiForEJBMessageBinding {{Ejb1 MessageBean ejb-jar-ic.jar,META-INF/ejb-jar.xml 9999}}}
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Ensure each non message-driven enterprise bean in your application or module is bound to a JNDI name. Use this option to provide missing data or update a task.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Note: This option only applies to a Network Deployment environment.
Example usage:
Using Jacl:
The last field of each entry specifies the isolation level. Valid isolation level values are 2 or 4.
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
The enterprise beans you install contain RunAs system identity. You can optionally change this identity to a RunAs role. Use this option to provide missing data or update a task.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Mapping a specific data source to a CMP bean overrides the default data source for the module that contains the enterprise bean. Use this option to provide missing data or update a task.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Mapping a specific data source to a CMP bean overrides the default data source for the module that contains the enterprise bean. Use this option to provide missing data or update a task.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
The last field in each entry of this task specifies the value for resource authorization. Valid values for resource authorization is cmpBinding.perConnectionFactory or container.
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
If you pre-deploy the application Enterprise Archive (EAR) file using the EJBDeploy tool then the default value is nodeployejb. If not, the default value is deployejb.
Possible values include the following:
CLOUDSCAPE_V5 DB2UDB_V72 DB2UDBOS390_V6 DB2UDBISERIES INFORMIX_V73 INFORMIX_V93 MSSQLSERVER_V7 MSSQLSERVER_2000 ORACLE_V8 ORACLE_V9I SYBASE_V1200
For a list of current supported database vendor types, run ejbdeploy -?.
The default value is: nodeployws.
This is the default setting.
Example usage:
Using Jacl:
The last field in each entry of this task specifies the value of the protection. Valid protection values include: methodProtection.denyAllPermission. You can also leave the value blank if you want the method to remain unprotected.
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
The last field in each entry of this task specifies the value of the protection. Valid protection values include: methodProtection.uncheck, methodProtection.exclude, or a list of security roles separated by commas.
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
where {{"All Role" No Yes "" ""} corresponds to the following:
"All Role" | is the role name |
No | indicates to allow access to everyone (yes/no) |
Yes | indicates to allow access to all authenticated users (yes/no) |
"" | indicates the mapped users |
"" | indicates the mapped groups |
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
Example usage:
Using Jacl:
Use the taskInfo command of the AdminApp object to obtain information about the data needed for your application. You only need to provide data for rows or entries that are missing information, or those where you want to update the existing data.
This option is the default setting.
This value is the default setting.
This value is the default setting.
The default setting is distributeApp.
This is the default setting.
This is the default setting. Use useMetaDataFromBinary to indicate that the metadata used at run time comes from the EAR file.
This is the default setting.
If you want to precompile JavaServer Pages files, specify it as a part of installation. The default is not to precompile JavaServer Pages files. The precompileJSPs option is ignored during deployment and JavaServer Pages files are not precompiled. The flag is set automatically using assembly tools.
The application that is being updated, specified by the appname option, must already be installed in the WebSphere Application Server configuration. The update action merges bindings from the new version with the bindings from the old version, uninstalls the old version, and installs the new version. The binding information from new version of the EAR file is preferred over the corresponding one from the old version. If any element of binding is missing in the new version, the corresponding element from the old version is used.
Applies only if you specify the update option.
Applies only if you specify the update option.
The default value is nouseMetaDataFromBinary which means that the metadata used at run time comes from the configuration repository.
The default setting is nousedefaultbindings.