To automate the startup of the Admin and managed server using WLST:
Note: If you are using P6 EPPM R8.2 or higher and you used the P6 EPPM Configuration Wizard to create the WebLogic domain, steps 1-6 below have already been completed.
call
setDomainEnv.cmd
java_home\bin\java.exe weblogic.WLST
where java_home is the path to the JDK installed and being used by WebLogic.
Note: If the "java_home" directory contains a space in the path, it should include quotations around the full path and executable being called. For example: "C:\Program Files\Java\jdk1.6.0_27\bin\java.exe" weblogic.WLST
connect('
weblogic','
password','
AdminServerHostName:
AdminServerPort')
where:
storeUserConfig('
p6home/scripts/primaveraConfig.secure', '
p6home/scripts/primaveraKeyfile.secure')
where p6home is the P6 home directory the you set during installation (for example, C:/p6home).
Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Do you want to create the key file? y or n
Note: Confirm that the following two files were created under the p6home/scripts directory: primaveraConfig.secure and primaveraKeyfile.secure. If these files were not created, repeat the previous steps.
<name>AdminServer</name>
<machine><!--NameOfMachine--></machine>
where <!--NameOfMachine-->
is the name of the logical machine created for the WebLogic domain.
Notes:
<machine><!--NameOfMachine--></machine>
above the <listen-address>
element.where <weblogic> is the Administrator user created for the WebLogic domain.
where <password> is the password for the Administrator user created for the WebLogic domain
Example path:
weblogic_home\user_projects\domains\your_domain\servers\<NameOfManagedServer>\data
Note: The username and password variables will become encrypted in the boot.properties file the first time the servers start using the node manager.
nmConnect(userConfigFile='
p6home/scripts/primaveraConfig.secure',userKeyFile='
p6home/scripts/primaveraKeyfile.secure',host='
NodeMangerHost',port='5556',domainName='
Mydomain',domainDir='
DomainLocation',nmType='ssl')
arg = "Arguments=\" -server -Xms128m -Xmx512m -XX:MaxPermSize=256m \""
prps = makePropertiesObject (arg)
nmStart('
AdminServer',props=prps)
connect(userConfigFile='
p6home/scripts/primaveraConfig.secure',userKeyFile='
p6home/scripts/primaveraKeyfile.secure',url='t3://
Adminserverhost:
Adminserverport')
start('
myManagedServer')
where:
Note: If multiple managed servers exist, repeat the line ‘start(‘myManagedServer’)’ with the name of each managed server.
SETLOCAL
SET CLASSPATH=
call
weblogic_home\user_projects\domains\
your_domain\bin\setDomainEnv.cmd
call
java_home\bin\java.exe weblogic.WLST
p6home\scripts\start_primavera.py
where:
Note: If the "java_home", "p6home" or "weblogic_home" directories contain a space in the path, it should include quotations around the full path and executable/command file being called. For example: call "C:\Program Files\Java\jdk1.6.0_27\bin\java.exe" weblogic.WLST C:\P6WebAccess\scripts\start_primavera.py
Using the WebLogic Scripting Tool on Windows
Starting the Node Manager with WebLogic
Adding the start_primavera.bat to the Windows Task Scheduler
Executing the start_primavera.bat file
Using WebLogic Scripting to Stop the WebLogic Domain for P6 EPPM
Legal Notices
Copyright © 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Monday, October 24, 2016