Professional Documents
Culture Documents
Summary
Symptom
Missing DB Pools (Portal and Metamatrix) and EISConnectors
More Terms
dbms PL SP 19 sap j2ee engine corrupted connect startup failure
Solution
o For creating the DB Pools the following has to be done:
1. Make sure that the J2EE server is running 2. In the SAPJ2EE server console, run the following commands (in case
that the server is running in background, please follow note 531293, which explains how to obtain a console in this case. if needed run on other servers in the cluster): a) add dbpool b) Depending on the database, issue the REGISTER_POOL commands For the Portal DB Pool (sapep): ------------------------------------------For Oracle Server issue as one line: REGISTER_POOL sapep -defConn:50 -maxConn:120 -initConn:0 -user:<DBUser> -password:<DBPassword> -driver:oracle.jdbc.OracleDriver -url:jdbc:oracle:thin:@<SERVER>:<PORT>:<SID> -library:com.sap.jdbc_driver_references -poolType:local For SQL Server issue as one line: REGISTER_POOL sapep -defConn:50 -maxConn:120 -initConn:0 -user:<DBUser> -password:<DBPassword> -driver:com.sap.portals.jdbc.sqlserver.SQLServerDriver "-url:jdbc:sap:sqlserver://<SQL Server Host>:<Port>;DatabaseName=<PCDDB Name>" -library:com.sap.data_direct_driver_references -poolType:local
For creating Metamatrix DBPool (MMPool): ---------------------------------------------------------For Oracle Server issue as one line: REGISTER_POOL MMPool -defConn:50 -maxConn:120 -initConn:0 -user:<DBUser>
25.09.2007 Page 1 of 3
Note 706216 -
-password:<DBPassword> -driver:oracle.jdbc.OracleDriver -url:jdbc:oracle:thin:@<SERVER>:<PORT>:<SID> -library:com.sap.jdbc_driver_references -poolType:local For SQL Server issue as one line: REGISTER_POOL MMPool -defConn:50 -maxConn:120 -initConn:0 -user:<DBUser> -password:<DBPassword> -driver:com.sap.portals.jdbc.sqlserver.SQLServerDriver "-url:jdbc:sap:sqlserver://<SQL ServerHost>:<Port>;DatabaseName=<PCD DBName>" -library:com.sap.data_direct_driver_references -poolType:local c) check the creation of Portal and Metamatrix DB Pools * run the following command GET_POOLS in the server console (after you run ADD DBPOOL) MMPool and sapep should be listed . * For checking a DB Pool properties, run the following command in the server console: GET_POOL_PROPS <DB Pool Name> * For checking the DB Pools , run the following commands in the server console: TEST_POOL MMPool SELECT * FROM MM_PRODUCTS Should result in 4 lines TEST_POOL sapep SELECT * FROM EP_ATTR_DEFS Should result in 6 lines -------------------------------------o For creating the 2 EISConnectors you should do the following (if needed repeat on the other servers in the cluster): a) Open the J2EE Admin Tool b) Go to Server-> Services c) Select the eisconnector service
d) Click the Add button. Look in the folder: UNIX: /usr/sap/<j2ee_instance_name>/j2ee/j2ee_ <instance_number>/services/connectors/ Windows: <installation drive>:\usr\sap\<j2ee_instance_name>\j2ee\j2ee_ <instance_number>\services\connectors\ e) Select the file for the SAP connector: f) Click OK. g) Select the file for the JDBC connector: h) Click OK. jdbcConnector.rar SAPCFConnector.rar
i) Restart the engine Another option to create the EISConnectors is available via the Portal Analyzer:
25.09.2007 Page 2 of 3
Note 706216 -
a) Go to the analyzer folder UNIX: /usr/sap/<j2ee_instance_name>/j2ee/j2ee_<instance_number>/analyzer Windows: <installation drive>:\usr\sap\<j2ee_instance_name>\j2ee\j2ee_<instance_number>\analyzer b) run the go command c) Run the analyzer on the Plug-ins: Connectors/Check JDBC Connectors Existence Connectors/CheckSAPConnectorsExistence d) Run the Fix on those Plug-ins.
Header Data
Release Status: Released on: Priority: Category: Main Component Released for Customer 06.09.2005 07:46:36 Recommendations/additional info Workaround for missing functionality EP-SYS-INS Installation
Valid Releases
Software Component EP-PSERV SAP-JEE Release 6.0 60 From Release 6.0 6.20 To Release 6.0 6.20 and Following
Related Notes
Number 711383 703570 Short Text Problems starting or running Metamatrix service in EP6 SP2. Avoiding redeploying from scratch after corruption of DBMS
25.09.2007
Page 3 of 3