Source Code Editor or IDE Database System and JDBC Driver Web Browser

1-16 Developing Applications for Oracle WebLogic Server prompt setenv ANT_OPTS=-Xmx128m If you want to set the heap size permanently, add or update the MEM_ARGS variable in the scripts that set your environment, start WebLogic Server, and so on, as shown in the following snippet from a Windows command script that starts a WebLogic Server instance: set MEM_ARGS=-Xms32m -Xmx200m See the scripts and commands in WL_HOMEserverbin for examples of using the MEM_ARGS variable.

1.13.2 Source Code Editor or IDE

You need a text editor to edit Java source files, configuration files, HTML or XML pages, and JavaServer Pages. An editor that gracefully handles Windows and UNIX line-ending differences is preferred, but there are no other special requirements for your editor. You can edit HTML or XML pages and JavaServer Pages with a plain text editor, or use a Web page editor such as Dreamweaver. For XML pages, you can also use an enterprise-level IDE with DTD validation or another development tool that supports editing of XML files.

1.13.3 Database System and JDBC Driver

Nearly all WebLogic Server applications require a database system. You can use any DBMS that you can access with a standard JDBC driver, but services such as WebLogic Java Message Service JMS require a supported JDBC driver for Oracle, Sybase, Informix, Microsoft SQL Server, or IBM DB2. Refer to Oracle Fusion Middleware Supported System Configurations at http:www.oracle.comtechnologysoftwareproductsiasfilesfus ion_certification.html to find out about supported database systems and JDBC drivers.

1.13.4 Web Browser

Most Java EE applications are designed to be executed by Web browser clients. WebLogic Server supports the HTTP 1.1 specification and is tested with current versions of the Firefox and Microsoft Internet Explorer browsers. When you write requirements for your application, note which Web browser versions you will support. In your test plans, include testing plans for each supported version. Be explicit about version numbers and browser configurations. Will your application support Secure Socket Layers SSL protocol? Test alternative security settings in the browser so that you can tell your users what choices you support. If your application uses applets, it is especially important to test browser configurations you want to support because of differences in the JVMs embedded in various browsers. One solution is to require users to install the Java plug-in from Sun so that everyone has the same Java run-time version.

1.13.5 Third-Party Software