Iplanet installation brief description
Keyword index:. Software installation. Management deployment. Development and commissioning. Reference
Part 1: Software installation 1. Introduction: IPlanet is an excellent product recommended by Sun's recommended Java application service, which contains two parts of IPlanet Web Server and IPlanet Application Server, which is very powerful, but this article only introduces some of the features support Java. .
2. Software version and environment: iPlanet Web Server 6.0 Iplanet Application Server 6.5 (Learning version) The operating system is WIN2000, 256M memory, but IPlanet Application Server recommends 512M memory, which is more resource.
3. Install IPLANET Web Server: Easily install it through the installation wizard, you need to customize the account password and the two listening port numbers (management ports and web ports), where to note that there are two options when configuring JDK First, it is self-defined using it. It is recommended to configure the first item, such as: JDK Path: D: /JDK1.3. This version currently supports JDK1.2, 1.3. Of course The JDK parameter can also be modified in the management interface after installation. You can access debugging after installation: http: // localhost: Port / Ports configured according to the installation can access the management end and the server separately, and the management section can also be from Windows Enter the start menu. If you visit, you will be successful.
4. Install IPLANET Application Server: IPLANET Web Server should be installed before installation, you must have a TCP / IP protocol, you also need to provide a domain name, such as Domain. In the installation service process, it comes with IPlaNet Directory Server is also required. Install this service to provide it with a SUFFIX: DC =, this is a custom ID. You can also fill in the Domain. The interface configuration web server will appear during the installation process. If you have already installed IPlanet Web Server (this is the installer Preferred), the installer automatically configures two connection support, and also publishes the same program to IPlanet Web Server. It is also possible to modify the web server listening port. There are also some configuration defaults, the database driver can be After installation, you can open the Samples Application from the Start menu after the installation is complete, you can display a number of sample portions and sample related introductory, but it only has Fortune (including session bean) on the Application Server, you can access The Fortune (Quick Test) connection under Sample Applications is successful, and the installation is successful. The second part management deployment
1. Deploying applications on iPlanet Web Server iPlanet Web Server can support deployment of enterprise-level applications such as EJB. Enter the management background to configure and modify JDK under global settings. Deploy the application's feature can be from Servers --- -Manage ---- Class Manager ---- DefaultClass ---- Manager ---- Web Application enters the following publish page publishing and managing applications, note that the APPLICATION URI should begin with "/".
2. Backstage management of IPLANET Application Server: Run the IAS Administration Tool from the Start menu to manage the Application Server.
Here is a few known parts.
General: You can configure some basic parameters, selecting Enable Dynamic Class Reloading to ensure the latest compilation of JSP each time.
Database: It is used to configure Datasouce. It provides two ways, the second should be self-contained, only the first relatively common Oracle's Thin connection. First To configure JDBC Drivers: Drivers Type: Custom Drivers Identification. Such as JDBC_TYPE4 Drivers ClassPath: Drive Class Path. Pooled Datasouce Name: Data Source Connection Pool Classification, Oracle.jdbc.Pool.OracleConnectionPoolDataSourceJDBC ClassName: Fill the above column first, this column will be blocked. Such as forced filling Will be wrong XA Datasouce Name: Oracle.jdbc.xa.client.OraclexadataSource This should be related to the class name. Next, you can configure Datasouce: Fill in JNDI Name in the Add window, select Drivertype just configured, then The UserName and Password are filled in. Select JNDI in the DataSouce Selection Box, add URL content to the Vendor Specific Properties, for example: URL: JDBC: Oracle: Thin: @ W22: 1521: Myora in modification Other related parameters can be.
You can also write XML documents with deployment tools to configure Datasouce, which is later described later.
Logging: You can activate the configuration-related log file.
Application: You can modify the path of some application services and see some of the operations of the configured Application. Because it is a learning version, the application's uninstall function is not implemented.
Backstage parameter configuration modification requires restarting the server to take effect, and can manage Server at the General option.
3 The deployment tool for IPLANET Application Server From the Start menu Run IAS Deployment Tool to publish an enterprise-level application service program in Application Server. Of course, these publishing work can also be more convenient to integrate with JBuilder. The operation interface is shown below:
The release station can be released * .ear, *. War, *. Jar package
Publishing process: First, you need to register a service through Tools ---- Register Server to entered during the installation process. If it is a package file, such as iplanet_home / as / as-sample package Can be published directly, the lower Result and Message window displays relevant information. For example, the successful release is usually needed. The sample can be accessed through the exemplary entrance that has been installed, or you can pass HTTP as other as you publish. // Host: Port / NASAPP / Publish Service Name / Formal Access.
If you are just some JSP and class files, you can pack and publish it by the release tool: New an Application or Module, enter the NAME, you can immediately generate it immediately, you can also generate it first, select the empty package INSERT generated by point. Note To transform the directory structure through the Resolve button during the Insert, it is generally removed until the selected file is red to blue. After adding all files, you can describe, configure the service with the Edit Descriptor. Note It is necessary to provide factory class when configuring entity beans: com.netscape.server.eb.sqlpersistenceManagerFactory Click Save to generate related XML files and save the package. Then release the generated package registration Datasouce: Tools ---- Register Datasouce; You can directly open an XML file to register, or you can use the input parameter save as an XML file. The sample XML file is as follows:
1. Integration with JBuilder7 is also very perfect. Select JBuilder's Tools ---- Configure Serves to select the iPlaNet Application Server 6.x in the left box, activate it on the right, configure Home, Other options Back to automatically configure, if you select Add IplanaT Tools to Tools Menu in Custom, you will find that there are more than three of the Tools of JBuilder. We have just become familiar with the function option. Develop, in the Project Properties Server Selection IPlaNet Application Server 6.x You can, the project will automatically generate the configuration file for definition IPLANET. The current learning version only supports EJB1.1 specification 2. JSP, servlet, and EJB development IPlanet to deploy the application to expand the package in his work directory. The default directory is under iplanet_hom / IAS / apps, for JSP, servlet, if Dynamic Class Reloading is configured in the background, then directly override, you can see new results for access. For EJB portions, you can also cover directly. But you usually need to restart your service before you can see a new message.
3. Debug If logging is configured in the background, you can use the IPlanaT_Home / IAS / LOGS to view the run log. You can also run iplanet_home / IAS / bin / kas -debug in the command mode, some bugs and debugging information will be printed into the console. If yes Published to web server, it will output to the corresponding log file, log directory is similar to: D: / IPlaNet / Servers / HTTPS-W22 / LOGS /
Part IV Reference
1. IPlanet Web Server has a more detailed document under its manual / https. 2. Iplanet Application Server may be a learning version, only online information, more detailed, such as http://docs.sun.com/source /816-5784-10/contents.htm http://docs.sun.com/source/816-5786-10/contents.htm In fact IAS, it is also a good learning reference.
