Configurations taken into consideration from Oracle recommendations.
Primavera version 8.3.2
Database 11.2.0.3 X86_64
Web based installation.
OS - Windows server 2003 X86_64 bit.
Weblogic - 11g (10.3.0.6 generic)
Java - Jrockit 28.2.5
You can have the installers from Oracle e delivery. Select option 8.3.0 for 8.3.2 as Oracle have removed the 8.3.0 dumps with 8.3.2.
1. Below are the installation steps.
2. Now start the Primavera application from the scripts provided by oracle in Primavera home under scripts directory.
3. Below is the output from the started script. start_Primavera.bat
E:\P6EPPM_1\scripts>start_Primavera.bat
CLASSPATH="E:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\Oracle\MIDDLE~1\patch_ocp371\p
rofiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Java\JROCKI~1.0\lib\tools.jar;E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webl
ogic_sp.jar;E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;E:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.6.0.j
ar;E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;E:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;E:\Oracle\MIDDLE~1\mod
ules\NETSFA~1.0_1/lib/ant-contrib.jar;"
PATH="E:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\native;E:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\native;E:\Oracle\MIDDLE~
1\WLSERV~1.3\server\native\win\x64;E:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;E:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Java\JROCKI~1.0
\jre\bin;C:\Java\JROCKI~1.0\bin;C:\app\product\11.2.0\dbhome_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Fi
les\Java\jdk1.7.0_40\bin;C:\Program Files\Java\jre7\bin;E:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\x64\oci920_8"
Your environment has been set.
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
PRM-Starting Primavera Admin Server, Managed Servers, and Deployments
PRM-Connecting to Node Manager...
Connecting to Node Manager ...
<Feb 25, 2014 6:38:19 PM GMT+05:30> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better start
up performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 25, 2014 6:38:20 PM GMT+05:30> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECD
RBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification
Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The load
ing of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.
840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G
3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trust
ed certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.1
1.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class
3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificat
e parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class
2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificat
e parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU
=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in t
he AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication Roo
tCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Uns
upported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Ce
rtification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loadi
ng of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.8
40.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,
O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<Feb 25, 2014 6:38:21 PM GMT+05:30> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certifica
tion Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate li
st raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Successfully Connected to Node Manager.
PRM-Starting AdminServer
Starting server AdminServer ...
Successfully started server AdminServer ...
Connecting to t3://localhost:8001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'PrimaveraP6EPPM'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
PRM-Starting managed server P6
Starting server P6 ................................................
Server with name P6 started successfully
PRM-Attempting to start deployments in case they were not started automatically
dr-- p6
PRM-Starting deployment p6
Starting application p6.
<Feb 25, 2014 6:40:15 PM GMT+05:30> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating start operation for application, p6 [archive:
null], to P6 .>
.Completed the start of Application with status completed
Current Status of your Deployment:
Deployment command type: start
Deployment State : completed
Deployment Message : [Deployer:149194]Operation 'start' on application 'p6' has succeeded on 'P6'
Disconnected from weblogic server: AdminServer
Successfully disconnected from Node Manager.
PRM-Startup Complete
PRM-Completed. Returned error level: 0
Exiting WebLogic Scripting Tool.
<Feb 25, 2014 6:40:22 PM GMT+05:30> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in wh
ich it was created.>
E:\P6EPPM_1\scripts>
No comments:
Post a Comment