cannot see JSP changes in QA

[Former Member]

Hello Experts,

l am new to this area so kindly bear with me if I am not able to explain my issue properly....

We made a change (added two new columns to the table being displayed from the RFC ) to one of the JSP pages and tested it in DEV and it worked properly. NWDI activities were then released and imported to QA successfully.

for some reason the change does not appear in QA system. Does anyone have any ideas on what the problem could be ??? any steps that I am missing ??

I have already checked the following...

1. activities have been imported to QA successfully.

2. checked the folders in the cons folder in DTR and the changed JSP pages appear there.

3. restarted the QA server.

4. R/3 changes have been transported and tested in QA.

nothing seems to work so far...would really appreciate any ideas to fix this...

Thanks,

Praveen.

[Former Member]

Hello Praveen,

You can try to get the "View Soruce" and check whether your changes are there in the JSP.

If it is not reflected there then this is a confirmation that your changes are not deployed into QA.

One Q:Also is this your first change??

Hope this helps in some way for this prob.

Regards,

Senthil.

[Former Member]

1. activities have been imported to QA successfully.

Are you sure that the changes have been deployed to QA? If automatic deploy is not set, import doesn't necessarily start the deploy. Check this in the deployer servlet - <NWDI-host>:<port>/TCS/Deployer

[Former Member]

Thanks Eswar for your quick response....

I went to the link an put a * in the Buildspace under Trigger Autodeployment. On hitting submit, I got a message saying auto deployment has been activated....I am not sure if it was always on....

But when i go to the QA buildspace in CBS and check my requests...they all have Request State as SUCEEDED, which means that the build was successful and so was deployment right ??

[Former Member]

Just a wild thought. Can you clear cache from your browser and try.

Pradeep

[Former Member]

You can always find the details from the log.

But, here is another tip. Get the access to the deployed application in QA (or ask Basis team to verify) and see if the modifed code is in fact deployed. This will rule out coding issue if the code is not deployed at all. You can focus on the deploy issue...