on 02-24-2011 9:43 AM
Dear experts,
I hope you can help me with this issue.
I few weeks ago I had to make some changes in an Java proxy because it was not connecting to a third party system.
I made these changes and imported this proxy using a SAP HOW TO guide and started working as desired.
The problem is that when we restart the PI system this proxy starts failing again and I have to reimport the java proxy again to make it work.
Maybe I am missing some necessary step, but I think that the changes I am making in the proxy are not permanent and I need to make them permanent.
We are using PI 7.0
Thanks for your help
Santiago
>> I made these changes and imported this proxy using a SAP HOW TO guide and started working as desired.
When you made changes and deployed in tht PI server, did you rename the ear file? Also delete the old deployed ear file and deployed only the latest one? If you make namechanges in the ear content such as jsp or servlet or enterprise bean and they will be available in cache too...
Tips: Check that you have only one Archive file for the java proxy and don't have redundant name for service components like jsp or servlet in it. Also, when we bring up java stack engine, it will load all the deployed ear in the application context. Check the logs and see any weird thing going on such as class not found exception or so...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Santiago,
After you make changes in EJB code. Follow the following steps to deploy the EAR file into PI server using NWDS
1) Re build you EJB project.
2) Create a new EAR file.
3) deploy the EAR file. ( you will need the J2EE_ADMIN access)
Refer this How to Work with Java proxies PDF:
Regards,
Aravind
User | Count |
---|---|
85 | |
10 | |
9 | |
9 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.