WebLogic 6.1 Configuration of Database Aspects
(1) Setting the ClassPath in the setEnv.cmd file under the beahome / weblogic6.1 / config / mydomain directory (set classpath = ....) Plus the driver of JDBC, such as $ oracle_home90 / jdbc / lib / class12. ZIP.
(2) Start WebLogic6.1
(3) Configure the connection pool and start the WebLogic 6.1 console. Click on the Connection Pools connection on the left, then click on the CONFIGURE A New JDBC Connection Pool ... connected to the right. One input:
Thin: (indicating that the database is accessed using pure Java, and the client support is not used)
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 supported by local Oracle clients)
Name
Cappool
URL
JDBC: WebLogic: Oracle
Driver classname
WebLogic.jdbc.oci.driver
PROPERTIES
User = hillfree
Password = HillFree
Server = Network Service Name (this is the Oracle database connection string configured by yourself, each may be different) WebLogic.codeet = GBK (Chinese display problem)
(4) Click the Connectios tab
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) Next, click Testing Tags
Test Table Name
Dual
At the same time, the two Checklist are selected.
(6) Next, click Targets Tags.
Select MyServer from Available to Chosen. Select the application button.
(7) Creating a data source
Click on the Data Sources tab on the left, then click Configure a New JDBC Data Source to connect on the right.
[Note]: The new workflow engine requires TX DataSource and select Two-Phase Commital.
Enter it under the Configuration tab
Name
WFDS
JNDI Name
WFDS
Pool Name
Cappool
Next, click Targets Tags
Select MyServer from Available to Chosen. Select the application button.
(8) Restart WebLogic 6.1
note:
1. If weblogic is started through the menu, add $ WL_HOME / BIN / OCI901_8 in the PATH system variable of the computer system; (the drive letter here may not be the same.) To support Oracle driver
2. If WebLogic is started in JBuilder, you should modify the value of VM parameters in Project -> Project Properties -> Run-> EJB, where the java.library.path section should be modified to: java.library.path = $ wl_home / bin / OCI901_8; E: /BeaHome/WLServer6.1/bin, the rest remains unchanged. (Pay attention to disk)! You can also set in Config Server
The configuration required in JBuilder7
(1) Install JBuilder7.0 and WebLogic6.1
(2) Select Configure Server in the Tools menu, select the WebLogic 6.x tab, fill in the tables in the inside, which is the parameters when installing WebLogic Server 6.x. The bottom USE EXTERNAL Compller of the page does not have to be selected, determine the return.
(3) Select Configure Libraries in the Tools menu, select the New button, enter the NAME of the dialog box, select the Add button, select Classes12.zip in the installed Oralce Client's JDBC / LIB directory . Select OK to return.
(4) Select Enterprise Setup in the Tools menu, select the Database Drivers tab, then select the Add button, select the LIB (Oracle) to build.
(5) Select Default Project Properties in the Project menu, select the Servers tab, then select the ... button, select WebLogic Application Server 6.x, select OK to return.
(6) Next, the development of EJB can be performed. It is recommended to develop EJB2.0.
(7) The database is currently installed on 172.20.54.234, the service listener is retained 1521, the SID is ORA9I, the user name HillFree, the password is HillFree.
note:
After writing EJB, if you compile error, it is likely that the path should be contained in the path indicated by the system variable TMP, TEMP, and ClassPath. Remove the path containing spaces, compile can be normal.
Precautions for using JB to develop Web Services
If you want to perform Web Services, you may need to put JBuilder7 / lib / jaxrpc.jar in the ClassPath prefare, because Borland has integrated a large number of third-party components in order to quickly launch a new version, which is insufficient for WebLogic environment. The conflict conflict, according to the first matching principle of CLASSPATH, it is easy to cause an error.
