Absent Member.. mkariro Absent Member..
Absent Member..
219 views

CONCURRENT_REQUEST_USER issue

Hi

I’m facing a strange issue.

 

Though I’ve set CONCURRENT_REQUEST_USER=oracle in server.conf still when PPM tries to retrieve the in/out logs from vision, it tries to login using username=ppm.

 

Following is the error:

Could not retrieve the logfile:

  Host:PMNALX0727

  Username:ppm

  File:/u06/oracle/orappsgpcomn/admin/log/orappsgp_pmnalx0727/l7734366.req

Could not retrieve the outfile:

  Host:PMNALX0727

  Username:ppm

  File:/u06/oracle/orappsgpcomn/admin/out/orappsgp_pmnalx0727/o7734366.out

 

Any thoughts?

 

Thanks

0 Likes
8 Replies
Absent Member.. Anjaiah Absent Member..
Absent Member..

Re: CONCURRENT_REQUEST_USER issue

I think,you have to setup those paths in application level..then only concurrent log files will save under server.

0 Likes
CGut Absent Member.
Absent Member.

Re: CONCURRENT_REQUEST_USER issue

Hi Mkairo,

Here are similar errors:

please take a look: http://support.openview.hp.com/selfsolve/document/KM192116
Also take a look to the following:

Error:

When trying to migrate Concurrent Requests, or any AOL object for that matter, the exec.log shows:

Could not retrieve logfile:
Host: SEASL031
Username: applmgr

File: /itgoa_dev/opt/appofs/fin_common/admin/log/SBD0B_seasl031/l
2775175.req
Could not retrieve outfile:
Host: SEASL031
Username: applmgr

File: /itgoa_dev/opt/appofs/fin_common/admin/out/SBD0B_seasl031/o
2775175.out

The links to the files are dead links, even though the files are there.


Solution:


Please follow these steps:

1. sh kConfig.sh (see the document on how to navigate to the oracle concurrent user settings)
2. sh Stop.sh -now -user admin *your user might be different
3. sh kUpdateHtml.sh
4. sh Start.sh

Below is sample output from the execution of these steps:

$ sh kConfig.sh -console
JAVA_HOME = /u1/java/j2sdk1.4.2_06
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)

-------------------------------------------------------------------------------
The IT Governance Center Configuration Tool is used to maintain the ITG Server.
This tool will allow the ITG Administrator to perform the following tasks.

Edit server.conf variables - Manage your server.conf file.

Configure Windows Services - On Windows platforms the ITG server is run as a
service. Use this option to change the server parameters or to sync them with
server.conf.

Change the Server Mode - The ITG Server can be run in several modes, depending
on the operations that are being performed [Note: requires restarting the
server].

Integrate the ITG server with a Documentum Content Server version 5.3 -
Integrate ITG Server with Documentums Content Server version 5.3 for advanced
Document Management services.

Generate Database Statistics - Improve database performance by generating
statistics.

Compile JSP Files - Improve server performance by precompile JSP files.


Press 1 for Next, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------
Please select from the following configuration choices.

[ ] 1 - Edit server.conf variables
[ ] 2 - Configure Windows Services
[ ] 3 - Change the Server Mode
[ ] 4 - Integrate the ITG server with a Documentum Content Server version 5.3
[ ] 5 - Generate Database Statistics
[ ] 6 - Compile JSP Files

To select an item enter its number, or 0 when you are finished: [0] 1


[X] 1 - Edit server.conf variables
[ ] 2 - Configure Windows Services
[ ] 3 - Change the Server Mode
[ ] 4 - Integrate the ITG server with a Documentum Content Server version 5.3
[ ] 5 - Generate Database Statistics
[ ] 6 - Compile JSP Files

To select an item enter its number, or 0 when you are finished: [0]


Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------


Welcome to the Mercury ITG Governance Center Configuration wizard.

You first will be presented with server configuration categories. After
selecting the categories that you would like to configure, you will be
presented with a series of corresponding server parameters. Required parameters
are marked in red. Please enter values for all required parameters.

Please consult the System Administrator guide for more information.

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------
The configuration wizard will walk you through the configuration of your ITG
Server

[ ] 1 - All Parameters
[ ] 2 - Server
[ ] 3 - Execution
[ ] 4 - LDAP
[ ] 5 - Attachments
[ ] 6 - Email Notification
[ ] 7 - Database
[ ] 8 - Client Connectivity
[ ] 9 - Oracle Applications
[ ] 10 - Custom Variables

To select an item enter its number, or 0 when you are finished: [0] 9


[ ] 1 - All Parameters
[ ] 2 - Server
[ ] 3 - Execution
[ ] 4 - LDAP
[ ] 5 - Attachments
[ ] 6 - Email Notification
[ ] 7 - Database
[ ] 8 - Client Connectivity
[X] 9 - Oracle Applications
[ ] 10 - Custom Variables

To select an item enter its number, or 0 when you are finished: [0]


Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------
Category > Oracle Applications

There variables need only be set when using Object*Migrator with ITG. These
variable only need be defined if ORACLE_APPS_ENABLED is set to true.


Instructs the system to enable or disable configuration fields
specific to Oracle Applications integration. To use Object*Migrator,
GL*Migrator, or Patch*Applicator this should be true.


com.kintana.core.server.ORACLE_APPS_ENABLED

[ ] 1 - false
[X] 2 - true

To select an item enter its number, or 0 when you are finished: [0]



Any valid user on the system containing the Oracle Applications
Server that can be used to retrieve (via FTP) concurrent request
output files. This is only required for use with the Object*Migrator.


com.kintana.core.server.CONC_REQUEST_USER [changl] oravis1



Password for the Concurrent Request User.


com.kintana.core.server.CONC_REQUEST_PASSWORD:



Transfer protocol to use when transferring Concurrent Request logs
and patching README files. Valid values are: FTP, SCP.


com.kintana.core.server.CONC_LOG_TRANSFER_PROTOCOL

[ ] 1 - FTP
[ ] 2 - SCP

To select an item enter its number, or 0 when you are finished: [0] 2


[ ] 1 - FTP
[X] 2 - SCP

To select an item enter its number, or 0 when you are finished: [0]


Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------
Please read the information below.



Select Next to save the configuration changes or back to continue editing.

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1


Generating Configuration files
Generating configuration files for all deployed ITG servers
Generating configuration files for CH_M901_60
Generating right-to-left style sheets for all deployed ITG servers
Generating right-to-left style sheets for CH_M901_60
0 files created.

-------------------------------------------------------------------------------
You have changed some server configuration parameters. Please shutdown and
restart the ITG Server.

Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay [1] 1

-------------------------------------------------------------------------------
All configuration operations have been completed. Please remember that
server.conf and server mode changes are not applied until the server is
restarted.

Press 3 to Finish or 4 to Redisplay [3] 3
$
$ sh kStop.sh -now -user admin
JAVA_HOME = /u1/java/j2sdk1.4.2_06
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
Password:
Success: immediate shutdown succeeded
$ sh kStatus
kStatus: kStatus: No such file or directory
$ sh kStatus.sh
JAVA_HOME = /u1/java/j2sdk1.4.2_06
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
Checking rmi://lime.merc-int.com:12501/KintanaServer
--> Server is not running! (Could not connect to rmi://lime.merc-int.com:12501/KintanaServer)

$ sh kUpdateHtml.sh
JAVA_HOME = /u1/java/j2sdk1.4.2_06
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
Updating JBoss configuration files
Generating configuration files for all deployed ITG servers
Generating configuration files for CH_M901_60
Updating kStart.sh
Updating right-to-left style sheets
Generating right-to-left style sheets for all deployed ITG servers
Generating right-to-left style sheets for CH_M901_60
66 files created.
Generating dms.conf
dms.conf existed. Not replaced.
$ sh kStart.shart.sh


Please let me know if this helped you!
Carolina.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Absent Member.. mkariro Absent Member..
Absent Member..

Re: CONCURRENT_REQUEST_USER issue

Carolina,

 

Thanks for your response.

 

I've performed these steps multiple times since past few days but the issue still remains.

 

My main issue is that even after setting up CONCURRENT_REQUEST_USER=oracle, PPM still tries to log onto the vision server with username=ppm to fetch the log files.

 

Cant figure out why it is using ppm user instead of oracle.

 

Thanks

Mahinder

0 Likes
Absent Member.. mkariro Absent Member..
Absent Member..

Re: CONCURRENT_REQUEST_USER issue

I can log in using the oracle user and look at the log files manually.

 

Where those paths need to be set?

0 Likes
Outstanding Contributor.. Loc_Nguyen_PPM Outstanding Contributor..
Outstanding Contributor..

Re: CONCURRENT_REQUEST_USER issue

Hi Mkriro,

 

Regarding you issues i found an case had situation like you. Please take a look.

 

User is not able to access the package migration status logs and receiving the error message such as

Could not retrieve the logfile:
Host:CDCXPD1124
Username:apkntprd
File:/lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/log/l5816738.req

What is the root cause and how to troubleshoot to fix?

 


The following mechanism is used when PPM application retrieves output files from the Object Migrator Primary Host after concurrent request is executed:

1. When a package is submitted, the Object Migrator Primary host, in this example, the host called “CDCXPD1124” is running concurrent request to perform oracle app migration task. After the job is done, it creates the output logs file under its base_path /lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/out/

How does PPM know this host information? Because an environment for Object Migrator Primary Host shall be defined in the PPM->WB for this host CDCXPD1124, and base_path is set to
/lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/out/ and the username/password is apkntdev/<its password>, protocol is SSH2/SCP2, thus PPM knows the user account/protocol to call the host in order to run the request and also where to write the log file.

 

2. In PPM server.conf file, watch dog service is enabled, concurrent request user and concurrent request password as well as transfer protocol in SCP2 are all set, why? Because watch dog service is going to use the concurrent user account from PPM server to remote host CDCXPD1124 via SSH2/SCP2 protocol to access the output file such as /lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/out/o5817801.out.

 

3. Once the file is reachable via watch dog service running in PPM app, it will transfer back to PPM server. How and where to put in PPM server?
We use com.kintana.core.server.SERVER_ENV_NAME parameter to define the PPM server in the WB, and we provide username/password to access PPM machine, and base_path is PPM_HOME directory, protocol is SSH2/SCP2. So the watch dog service can SCP the outputs file from the object migrator host back into PPM server then put it in the transfer logs under base_path of PPM home.

If all these steps are successfully executed, then the execution log will be properly reviewed in WB. Based on this mechanism behind, we shall check all configurations involved in the steps above:

 

1. In server.conf file, for the concurrent user name and concurrent user password, they must be correct.
The password must be set by running kConfig.sh in ppm_home\bin, not by any other encryption tool.
How to test if this user name/password that you get is correct?
On PPM server, run scp command to the host CDCXPD1124 using the username such as apkntdev and password you receive, to verify if it can SCP into the host, and further down if it can access the directory such as /lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/out/, if you get error about wrong user info or permission, then you know what to fix.

 

2. Log into PPM app->WB, look for the ENV name “KINTANA_SERVER”, because this value is defined in server.conf file for parameter com.kintana.core.server.SERVER_ENV_NAME.
Open this ENV, and in its server section, you must provide username/password for accessing this PPM server, base_path is the base_path of PPM_HOME, (the same as you set in server.conf file), protocol must use SSH2 and Secure Copy 2, after that, run ENV Checker to make sure that it passes server checking.

 

3. In WB, look for the ENV name where the Object Migrator Primary Host is, check its server section to confirm if the username is apkntdev, and password is the concurrent request password, base_path should be /lv02/sw/apkntdev/inst/apps/kntdev_cdcxpd1124/logs/appl/conc/out/
Protocol should be SSH2 and Secure Copy 2. Again, run ENV Checker to make sure that it passes server checking.

 

4. In server.conf file, double confirm the following parameter values:

com.kintana.core.server.CONC_LOG_TRANSFER_PROTOCOL=SCP2 
com.kintana.core.server.CONC_REQ_TRANSFER_PROTOCOL=SCP2
com.kintana.core.server.TURN_ON_CONCURRENT_REQUEST_WATCHDOG=true
com.kintana.core.server.ORACLE_APPS_ENABLED = true

 

*  Pay attention on the red lines.

 

Hope this help.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
Absent Member.. mkariro Absent Member..
Absent Member..

Re: CONCURRENT_REQUEST_USER issue

Still same issue 😞

 

Thanks for your response.

 

Main issue is that PPM still uses username=ppm though we have configured CONCURRENT_REQUEST_USER=oracle.

 

Regards

Mahinder

0 Likes
CGut Absent Member.
Absent Member.

Re: CONCURRENT_REQUEST_USER issue

Mkairo,

The best way to proceed is opening a case in order to have a more explanation of the issue and provide you a effective solution, I will contact you by a private message.

Carolina.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
CGut Absent Member.
Absent Member.

Re: CONCURRENT_REQUEST_USER issue

The following is the resolution from the case opened by this thread:

Launch kConfig.sh and re-enter all parameters pertaining to Oracle apps. Re- enter the concurrent username and password.

Please also consider visiting the web-based version of this response at:
http://support.openview.hp.com/selfsolve/document/KM01139461


Thanks for your patience and for contacting HP support.

Best Regards,
Carolina.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.