How to start P6 Primavera R15.1 server step by step

First, we start AdminServer

[access@ptud PrimaveraP6EPPM]$ pwd
/home/access/fmw/user_projects/domains/PrimaveraP6EPPM

[access@ptud PrimaveraP6EPPM]$ ls
autodeploy console-ext           init-info nodemanager servers
bin         edit.lok              lib        pending      startWebLogic.sh
config      fileRealm.properties log.out    security     tmp
[access@ptud PrimaveraP6EPPM]$ ./startWebLogic.sh
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=256m
.
CLASSPATH=/home/access/setup/jdk/lib/tools.jar:/home/access/fmw/wlserver/server/lib/weblogic_sp.jar:/home/access/fmw/wlserver/server/lib/weblogic.jar:/home/access/fmw/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/home/access/fmw/wlserver/modules/features/oracle.wls.common.nodemanager_2.0.0.0.jar:/home/access/fmw/wlserver/../oracle_common/modules/com.oracle.cie.config-wls-online_8.1.0.0.jar:/home/access/fmw/wlserver/common/derby/lib/derbyclient.jar:/home/access/fmw/wlserver/common/derby/lib/derby.jar:/home/access/fmw/wlserver/server/lib/xqrl.jar
.
PATH=/home/access/fmw/wlserver/server/bin:/home/access/fmw/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/home/access/setup/jdk/jre/bin:/home/access/setup/jdk/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/access/bin
.
***************************************************
* To start WebLogic Server, use a username and   *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Starting WLS with line:
/home/access/setup/jdk/bin/java -server   -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/home/access/fmw/wlserver/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true   -Djava.endorsed.dirs=/home/access/setup/jdk/jre/lib/endorsed:/home/access/fmw/wlserver/../oracle_common/modules/endorsed -da -Dwls.home=/home/access/fmw/wlserver/server -Dweblogic.home=/home/access/fmw/wlserver/server     -Dweblogic.utils.cmm.lowertier.ServiceDisabled=true weblogic.Server

[
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4

Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Fri Mar 22 03:12:27 ICT 2002,
               To: Wed Mar 23 03:12:27 ICT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [    33f10648 fcde0deb 4199921f d64537f4]

Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
]

]
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7   06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84   81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4   B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC   90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<

]. The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>

Aug 21, 2015 9:00:49 AM weblogic.wsee.WseeCoreMessages logWseeServiceStarting
INFO: The Wsee Service is starting

Secondly, We run scripts to start p6.

[access@ptud scripts]$ pwd
/home/access/p6/scripts
[access@ptud scripts]$ ls
domain.properties primaveraConfig.secure stop_Primavera.py
domain_validator.py primaveraKeyfile.secure stop_Primavera.sh
newp6eppm.jar start_Primavera.py
primavera_config.py start_Primavera.sh

[access@ptud scripts]$ ./start_Primavera.sh
CLASSPATH=/home/access/setup/jdk/lib/tools.jar:/home/access/fmw/wlserver/server/lib/weblogic_sp.jar:/home/access/fmw/wlserver/server/lib/weblogic.jar:/home/access/fmw/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/home/access/fmw/wlserver/modules/features/oracle.wls.common.nodemanager_2.0.0.0.jar:

PATH=/home/access/fmw/wlserver/server/bin:/home/access/fmw/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/home/access/setup/jdk/jre/bin:/home/access/setup/jdk/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/access/bin:/home/access/fmw/wlserver/../oracle_common/modules/org.apache.maven_3.0.5/bin

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 ...

PRM-Node Manager does not appear to be running. Attempting to start and reconnect...
Connecting to Node Manager ...
Successfully Connected to Node Manager.
PRM-Starting AdminServer
Starting server AdminServer ...
Error Starting server AdminServer: weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for WebLogic server 'AdminServer' failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server 'AdminServer' log for detailed information.]. Please check Node Manager log for details.
Connecting to t3://localhost:7005 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-Starting managed server P6IntegrationAPI
Starting server P6IntegrationAPI ............................................
Server with name P6IntegrationAPI started successfully
PRM-Starting managed server P6WebServices
Starting server P6WebServices .......................................................................................................................
Server with name P6WebServices started successfully
PRM-Starting managed server TeamMember
Starting server TeamMember ..................................................................................................................................
Server with name TeamMember started successfully
PRM-Starting managed server p6procloudconnect
Starting server p6procloudconnect ..................................................................................................................................................
Server with name p6procloudconnect started successfully
PRM-Attempting to start deployments in case they were not started automatically
dr--   PrimaveraAPI
dr--   p6
dr--   p6help
dr--   p6procloudconnect
dr--   p6tm
dr--   p6ws
dr--   tmhelp

PRM-Starting deployment PrimaveraAPI
Starting application PrimaveraAPI.

...Completed the start of Application with status completed
Current Status of your Deployment:
Deployment command type: start
Deployment State : completed
Deployment Message : no message
PRM-Starting deployment p6
Starting application p6.

....Completed the start of Application with status completed
Current Status of your Deployment:
Deployment command type: start
Deployment State : completed
Deployment Message : no message
PRM-Starting deployment p6help
Starting application p6help.

.Completed the start of Application with status completed
Current Status of your Deployment:
Deployment command type: start
Deployment State : completed
Deployment Message : no message
PRM-Starting deployment p6procloudconnect
Starting application p6procloudconnect.

.Completed the start of Application with status completed
Current Status of your Deployment:
Deployment command type: start
Deployment State : completed
Deployment Message : no message
Disconnected from weblogic server: AdminServer
Successfully disconnected from Node Manager.
PRM-Startup Complete
PRM-Completed. Returned error level: 0

Exiting WebLogic Scripting Tool.

Now P6 web we can access via browser

You can shutdown P6 run scripts:
[access@ptud scripts]$ ls
domain.properties primaveraConfig.secure stop_Primavera.py
domain_validator.py primaveraKeyfile.secure stop_Primavera.sh
newp6eppm.jar start_Primavera.py
primavera_config.py start_Primavera.sh
[access@ptud scripts]$ ./stop_Primavera.sh
CLASSPATH=/home/access/setup/jdk/lib/tools.jar:/home/access/fmw/wlserver/server/lib/weblogic_sp.jar:/home/access/fmw/wlserver/server/lib/weblogic.jar:/home/access/fmw/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/home/access/fmw/wlserver/modules/features/oracle.wls.common.nodemanager_2.0.0.0.jar:

PATH=/home/access/fmw/wlserver/server/bin:/home/access/fmw/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/home/access/setup/jdk/jre/bin:/home/access/setup/jdk/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/access/bin:/home/access/fmw/wlserver/../oracle_common/modules/org.apache.maven_3.0.5/bin

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-Stopping Primavera Admin Server, Managed Servers, and Deployments
PRM-This will NOT attempt to stop the Node Manager as it may be
PRM-needed for other servers on this machine.
Connecting to t3://localhost:7005 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-Shutting down managed server P6
Shutting down the server P6 with force=true while connected to AdminServer ...
.....
PRM-Shutting down managed server P6IntegrationAPI
Shutting down the server P6IntegrationAPI with force=true while connected to AdminServer ...
..............
PRM-Shutting down managed server P6WebServices
Shutting down the server P6WebServices with force=true while connected to AdminServer ...
...
PRM-Shutting down managed server TeamMember
Shutting down the server TeamMember with force=true while connected to AdminServer ...
...
PRM-Shutting down managed server p6procloudconnect
Shutting down the server p6procloudconnect with force=true while connected to AdminServer ...
........
PRM-Shutting down AdminServer
Shutting down the server AdminServer with force=true while connected to AdminServer ...
..WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: AdminServer
Disconnected from weblogic server: AdminServer
PRM-Shutdown Complete

Exiting WebLogic Scripting Tool.