The OC4J administration user name and password. The user name for the default administrator account is oc4jadmin. OC4J must already be running before admin. The user-defined application deployment name, used to identify the application within OC4J.
The directory to deploy the EAR to. The deployed EAR file is also copied to this directory. Each successive deployment will cause this EAR file to be overwritten.
Optional The parent application of this application. The default is the global or default application. You can optionally specify the path and file name of the JAR to output the generated stubs to. For example:. The following example binds the utility application and its utility-web Web module to the default OC4J Web site:. The user-defined name of the application, which is the same name used for -deploymentName in the -deploy option. The name of the Web module.
WAR extension. The context root for the Web module. The following command removes an application from the OC4J runtime and removes bindings from any Web sites to which the application's Web modules were bound.
Note: The optional -keepFiles subswitch, which could be used to prevent files from being removed from the installed directories, has been deprecated. All files are now removed during undeployment. The syntax for -updateEJBModule is as follows: java -jar admin.
The path and file name of the RAR file to deploy. The user-defined connector name, used to identify the connector within OC4J. Include to grant all runtime permissions requested by the resource adapter, if required. The syntax is as follows. Note that the connector name must be supplied. All rights reserved. Home Solution Area Contents Index. Solution Area. The host name and port of the OC4J server on which you are invoking admin. Optional The parent application of this application.
The user-defined name of the application, which is the same name used for -deploymentName in the -deploy option. The name of the Web module.
The context root for the Web module. The following sections discuss each of them and summarize the relationships between them:. The servlet specification defines the concept and DTD of a Web descriptor, called web. The web. See the servlet specification for more information. Here is a sample web. It is typically global-web-application. This descriptor defines default behavior for Web applications in OC4J.
The global Web application descriptor is defined by the DTD orion-web. The orion-web. For detailed information about the elements and attributes of the OC4J global Web application descriptor, including the DTD and a hierarchical representation, see "Configuration for global-web-application. See "Sample global-web-application. In addition to the standard Web descriptor, web.
You can provide an orion-web. Use orion-web. Including an orion-web. Otherwise, OC4J generates orion-web. Additionally, some web. For detailed information about the elements and attributes of the OC4J-specific Web descriptor, including the DTD and a hierarchical representation, see "Configuration for global-web-application.
You can think of the relationship between global-web-application. The global-web-application. The key functions of a Web site XML file are the following:. It binds specified Web modules to the Web site, identifying each Web module to bind, the J2EE application it belongs to, and the context path portion of the URL to use in accessing it. It defines key settings for the Web site, such as the host name, port number, and protocol.
Each of these elements specifies the path and file name for the corresponding Web site XML file, as in the following sample server. In Oracle Application Server, there is just one Web site. An application attribute to specify the name of the J2EE application to which the Web module belongs the same as the EAR file name without the.
A name attribute to specify the name of the Web module the same as the WAR file name without the. A root attribute to specify the context path on this Web site to which the Web module is to be bound. In Oracle Application Server, it is used for some system-level functionality but is not otherwise meaningful.
See "Sample default-web-site. This example shows how an entry in server. The Web module is defined in the application. The Web site XML file, my-web-site. As a convention, though, use the same setting in both places. In an Oracle Application Server environment, the default-web-site. In an OC4J standalone environment, the http-web-site. The following sections review the structure of these files:.
This section reviews the standard J2EE application structure, which you can use as your development structure as appropriate. This discussion also shows the relative locations of optional OC4J-specific descriptors. The Web portion is marked in bold type. This portion reflects the structure of WAR files used to deploy Web modules.
At the top level are static pages such as index. This structure is defined in the J2EE specification and related specifications. The J2EE specification is at the following location:. This example shows the structure of the archive files for a simple Web application.
Following are the contents of utility. Optionally, you could also include an orion-application. Instead, in this example, one would be generated by OC4J during deployment. Optionally, you could also include an orion-web.
See the following site for information about ant :. This section reviews some preliminary considerations and then discusses several scenarios for deployment to OC4J standalone.
The primary deployment scenario is to use the admin. See "Application Packaging" for more information about structure and packaging. Key features are discussed here. In addition, this section considers alternative deployment scenarios that you may find useful during development, such as manually creating and populating a J2EE application structure or deploying an independent WAR file into the OC4J default application.
Before using the admin. By default, there is a user admin with administrative privileges, as specified in the following sample jazn-data. For the default administrative user admin , the default password is welcome , as in the following sample jazn-data. The file is automatically rewritten later to obfuscate the specified password. You will be prompted for the desired password.
This section provides a quick review of how to start and stop OC4J standalone. See the previous section, "Setting Up an Administrative User and Password" , for information about adminuser and adminpassword. The following sections discuss features and configuration of the OC4J default application and default Web application.
Some of the OC4J standalone deployment scenarios described later will use these features. OC4J is installed with a default configuration that includes a default application also known as the global application. By default, the OC4J server. In a typical OC4J installation, the default application contains a default Web application.
The name and root directory path of the default Web application are specified in the global application descriptor, and the default Web application is bound to a Web site through the http-web-site. This section details the default configurations for the OC4J default application and default Web application. In server. The name attribute specifies its name, and the path attribute specifies what to use as the OC4J global application descriptor:.
The specified descriptor for the default application or global application , application. To deploy to the default Web application, place your files under this directory according to the standard Web application structure. By default, the default Web application is bound to a Web site in the http-web-site. Here is an example:. This discussion assumes that if you modify your code, you would then repackage it and redeploy it. See "Setting Up an Administrative User and Password" for information about adminuser and adminpassword.
For -deploymentName , specify the desired application name, by convention the same as the EAR file name without the. The OC4J-specific descriptors—at a minimum, orion-application. This element specifies the application name, according to the -deploymentName setting in admin. After you have deployed your application, you can use the OC4J admin. Note the following:. The appname is the application name, according to the -deploymentName setting when you deployed it. The webappname is the name of the Web application.
This is the WAR file name without the. The websitename is indicated by the Web site XML file name for the desired site, without the. This example illustrates the result of deploying the utility. Here are the admin. In this example, the administrative account name is admin and the password is welcome.
The Web application name within utility. Typically, you would use standalone for development or for a simple single OC4J instance Web solution.
Download the OC4J Standalone User's Guide for information on how to start, stop, configure, and manage your standalone process. Make sure that it is a version that OC4J supports:. Some suppliers bundle a JDK with their products. If necessary, remove any old version s , replace them with a supported version, and update the appropriate environment variables.
Aside from this book, the rest of the OC4J documentation set was written with a standalone mindset. These other books may refer to modifying XML files by hand for managing the instance. This book provides a good overview and familiarization of the Oracle Enterprise Manager 10 g configuration pages.
You should be able to look at an XML representation and match it to the relevant Oracle Enterprise Manager 10 g field names. Also, the Distributed Configuration Management DCM utility, dcmctl , provides a command-line alternative to using Oracle Enterprise Manager 10 g for some management tasks. The dcmctl tool uses the same distributed architecture and synchronization features as Oracle Enterprise Manager 10 g , thereby providing identical functionality in a format that is ideal for scripting and automation.
Figure illustrates this as follows:. The default port number is Skip Headers.
0コメント