One of the most painful things is to have pdjrte installed incorrectly for the first time. If everything is installed as per needs and correctly in one time success , the journey is sweet. If not , or just in case you have to make any change , its more easy to unconfigure and then configure the system back. Trying to get one component, then second and so on will make you lose the mission critical time. To configure the pdjrte with already configured policy server be:
[root@tdiserver sbin]# ./pdjrtecfg -action status
HPDBF0031E This Java Runtime Environment has already been configured.
[root@tdiserver sbin]# ./pdjrtecfg -action name
Access Manager Runtime for Java
[root@tdiserver sbin]# ./pdjrtecfg -action unconfig
Unconfiguration of:
Access Manager Runtime for JavajvmHome: //V7.0/jvm/jre
is in progress. This might take several minutes.
Unconfiguration of: Access Manager Runtime for Java
completed successfully.
[root@tdiserver sbin]# ./pdjrtecfg -action config -interactive
Specify the full path of the Java Runtime Environment (JRE)
to configure for Tivoli Access Manager [//V7.0/jvm/jre]://V7.0/jvm/jre/
Enter 'full' or 'standalone' for the configuration type [full]:
Policy server host name [tdiserver]: policyserverfullname.company.com
Tivoli Access Manager policy server port number [7135]:
Enter the Access Manager policy server domain [null]:
The domain contains invalid characters.
Enter the Access Manager policy server domain [null]: null
Tivoli Common Directory logging is currently configured.
You may enable this application to use Tivoli Common Directory logging
using the currently configured directory for log files.
Do you want to use Tivoli Common Directory logging (y/n) [n]? y
Log files for this application will be created
in directory: /var/ibm/tivoli/common
Configuration of Access Manager Runtime for Java is in progress.
This might take several minutes.
Configuration of Access Manager Runtime for Java completed successfully.
[root@tdiserver sbin]#
---
This completes the pdjrte re-configuration to prevent any mishaps and make sure it works correctly
[root@tdiserver sbin]# ./pdjrtecfg -action status
HPDBF0031E This Java Runtime Environment has already been configured.
[root@tdiserver sbin]# ./pdjrtecfg -action name
Access Manager Runtime for Java
[root@tdiserver sbin]# ./pdjrtecfg -action unconfig
Unconfiguration of:
Access Manager Runtime for JavajvmHome: /
is in progress. This might take several minutes.
Unconfiguration of: Access Manager Runtime for Java
completed successfully.
[root@tdiserver sbin]# ./pdjrtecfg -action config -interactive
Specify the full path of the Java Runtime Environment (JRE)
to configure for Tivoli Access Manager [/
Enter 'full' or 'standalone' for the configuration type [full]:
Policy server host name [tdiserver]: policyserverfullname.company.com
Tivoli Access Manager policy server port number [7135]:
Enter the Access Manager policy server domain [null]:
The domain contains invalid characters.
Enter the Access Manager policy server domain [null]: null
Tivoli Common Directory logging is currently configured.
You may enable this application to use Tivoli Common Directory logging
using the currently configured directory for log files.
Do you want to use Tivoli Common Directory logging (y/n) [n]? y
Log files for this application will be created
in directory: /var/ibm/tivoli/common
Configuration of Access Manager Runtime for Java is in progress.
This might take several minutes.
Configuration of Access Manager Runtime for Java completed successfully.
[root@tdiserver sbin]#
---
This completes the pdjrte re-configuration to prevent any mishaps and make sure it works correctly
No comments:
Post a Comment