ZDS

Kintana Techniques

When you migrate a Standard AOL: object using Kintana, the package line waits for Oracle Applications to ftp back the log and out files generated by the Concurrent Manager request.

If things are not configured correctly, you will get 'Could not retrieve' messages in the execution log instead of valid links to the out and log files:

In order to resolve this you need some background on how Object Migrator works

When you run a Standard (e.g 'Aol:GUI Menu' ) object migration the PPM package creates a request in (Oracle Corp's) Concurrent Manager on the server hosting Oracle Applications (usually co-located on the server hosting the Kintana database).

Concurrent Manager then:

Runs a 'Request' to process the object.

Sends back to the PPM package the request Id it has assigned to the request which the package displays as line status e,g. 'Submitted (ConcReq :239967).

Outputs an 'out' file (with name formed as e.g. 'o239967' where the prefix is a lower case alphabetic Oh, and the number is the RequestId assigned by Concurrent Manager.

Outputs a 'log' file (with name formed as e.g. 'l239967' where the prefix is a lower case alphabetic 'ell', (NOT a numeric 1 !) and the number is the Request Id assigned by Concurrent Manager.

When it's completed the request, sends the PPM package the current status which Kintana displays as either 'Succeeded(ConcReq304575)' or 'Failed(ConcReq304575).

The PPM line needs to get back the out and log files. To do so it runs sql like this:

select logfile_name,outfile_name logfile_node_name, outfile_node_name
from fnd_concurrent_requests
where request_id = 304575

LOGFILE_NAME                                LOGFILE_NODE_NAME                           OUTFILE_NODE_NAME
------------------------------------------  ------------------------------------------  -----------------
/PA/45/kntacomn/admin/log/knta/l304575.req  /PA/45/kntacomn/admin/out/knta/o304575.out  HPUX22

The first part of the paths (down to the file name) tell Kintana where Concurrent Manager placed the out and log files. You or your Oracle Applications administrator will have set up these directories. The names will be specific to each user site.

To support out and log file retrieval the PPM Package uses an ftp account with read-only privileges set up on the server hosting Concurrent Manager (HPUX22). Matching entries for this account must exist in server.conf.

The PPM Package then looks up these ftp account entries in server.conf:

 com.kintana.core.server.CONC_REQUEST_USER=concmgrknta
 com.kintana.core.server.CONC_REQUEST_PASSWORD=
 

and starts up an ftp session to the server hosting Oracle Applications:

FtpClient: Socket opened to hpux22, port 21
logs on as concmgrknta
FtpClient: LOGON_ATTEMPT concmgrknta@hpux22:21
supplies the conuser password:
FtpClient: Reply to PASS : 230 User concmgrknta logged in.  Access restrictions apply.
FtpClient: CWD /PA/45/kntacomn/admin/out/knta/

and, issues a change directory command with the path down to knta/ that it got from the dynamic sql query:

Ftplient: CWD /PA/45//kntacomn/admin/out/knta/

The landing zone for the concurrent user ftp account MUST be set at the DIRECTORY ABOVE THE last directory in the path(s) returned by the above sql query.

If this is not done the ftp transfer back to the application server of the log and outfiles for the request will fail with 'Unable to retrieve' message in the package line execution log!

If the landing zone is set correctly the package will ftp the out and req files back to the application server, place them in {ITG_HOME}/logs/PKG_nnnnn/line(x), and the links on the execution log will resolve correctly.

Run the sql query to get the paths

Set up a temporary environment and enter the Server section fields for the CONC_REQUEST_USER ftp account.

Use the [Check] button and run a Server : FTP Server connection test to verify that the Base path is set correctly for the landing zone.

Kintana™ and 'HP PPM (Project and Portfolio Management)'™ are trademarks of Hewlett Packard Corporation.