WebLogic 6.1 / 7 + + Oracle9i development JBuilder7
Abstract: WebLogic 6.1 / 7 + + Oracle9i development JBuilder7
: WebLogic6.1 in the configuration database
(1) under the directory in BeaHome/weblogic6.1/config/mydomain setenv.cmd CLASSPATH set in the document (set CLASSPATH =….) Plus jdbc drivers, such as: $ ORACLE_HOME90 \ jdbc \ lib \ classes12 . zip.
(2) start Weblogic6.1
(3) configuration connection pool, start Weblogic6.1 console. Click on the left Connection Pools link, and then click on the right of the Configure a new JDBC Connection Pool … connected. An Input:
Thin: (a pure Java that access to the database, do not use the client support)
Name CapPool
URL jdbc: oracle: thin: @ 172.20.54.234:1521: ora9i
Driver Classname oracle.jdbc.driver.OracleDriver
Properties user = msc
Password = msc
Jdriver: (Access database is used to support local Oracle client)
Name CapPool
URL jdbc: weblogic: oracle
Driver Classname weblogic.jdbc.oci.Driver
Properties user = Hillfree
Password = Hillfree
= Server network services (this is their own machines configured Oracle database connection string, each person may be different)
GBK Weblogic.codeset = (Chinese that the problem)
(4) Click Connectios labels
Initial Capacity: 1
Maximum Capacity 10
Capacity Increment 2
Login Delay Seconds: 10
Refresh Period 10
Shrink Period 15
Prepared Statement Cache Size 10
(5) Testing then click on labels
Test Table Name
Dual
At the same time the two selected checklist.
(6) Then click Targets labels
Available from the election to myserver chosen. Select the Apply button.
(7) Create Data Source
Click Data Sources labels left, and then right click on Configure a new JDBC Data Source Link.
[Note]: a new workflow engine needs Tx DataSource, and selected two-phase commit.
Input in the Configuration tab
Name WFDS
JNDI Name WFDS
Pool Name CapPool
Then click Targets labels
Available from the election to myserver chosen. Select the Apply button.
(8) restart Weblogic6.1
NOTE:
1. If activated Weblogic menu, it should be in the computer system path variable system inside with a $ WL_HOME \ bin \ oci901_8; (here may not be the same letter.) To support Oracle Driver
2. If Jbuilder to start Weblogic, should be amended in the Project -> Project Properties -> Run-> Ejb the value of the VM parameters, which should be revised as part of java.library.path: java.library.path = $ WL_HOME / bin / oci901_8; E: / BeaHome/wlserver6.1/bin remaining unchanged. (Note letter)!
Can be set up in the Config Server
JBuilder7 in the desired configuration
(1) installed Jbuilder7.0 and Weblogic6.1
(2) In the Tools menu, select Configure Server, WebLogic 6.x labels choose to fill out the forms inside that WebLogic Server 6.x installed at those parameters. Pages bottom of the Use external compller would not have chosen to determine the return.
(3) In the Tools menu, select Configure Libraries, select New button, the pop-up dialog Name input Oracle (casually name), choose the Add button, the installation of the jdbc Oralce Client \ lib directory classes12 choice. zip. Back to choose ok.
(4) In the Tools menu, choose Enterprise Setup, select Database Drivers labels, and then select the Add button, select Step built lib (Oracle).
(5) in the Project menu, select Default Project Properties, select Servers labels, and then choose… button, select Weblogic Application Server 6.x, select ok to return.
(6) can be followed on the EJB development. Proposed development with EJB2.0.
(7) database is currently installed in the 172.20.54.234, service monitoring fracture reservations default 1521, SID is ora9i, hillfree user name, password is hillfree.
NOTE:
Write EJB, if compiler error, it is possible for the system is variable TMP, TEMP, classpath expressed by the path containing spaces. Contain spaces removed from the path, the compiler may be normal.
JB use when developing Web Services for attention if we are to the development of Web Services, and the possible need to jBuilder7/lib/jaxrpc.jar on classpath forefront, it is because Borland to quickly introduce new versions of a large number of integrated third-party components , the lack of testing on the WebLogic environment, causing Chongming conflict, in accordance with the principle of classpath the first match, is likely to result in procedural errors.
Bill-switched from: csdn Java, java, J2SE, j2se, J2EE, j2ee, J2ME, j2me, ejb, ejb3, JBOSS, jboss, spring, hibernate, jdo, struts, webwork, ajax, AJAX, mysql, MySQL, Oracle, Weblogic, Websphere, scjp, scjd
↑ Back
Tags: weblogic