Restart J2EE after RFC re-import

[Former Member]

Hi all,

It is necessary or is there another workaround in order to avoid the Restart of the J2EE after RFC re-import?

I was wondering if this is really necesary because in mayor developments scenarios, all the developers must stops their developments in order to one of them gets the reimport of their RFC.

Any suggestions or comment would be appreciated.

Regards,

Orlando Covault

[Former Member · Accepted solution]

Hi

It is recommended to restart the J2EE Engine after reimporintg the model because metadata will not be refreshed,

The Web Dynpro Adaptive RFC framework sits on the top of several layers such as the Java Connector Objects (JCO), Data Dictionary (DDIC) and the MDI.

After the first access each of these layers caches the metadata within them and keeps returning the cached values thereafter. The caches are not refreshed even if something would have changed in the metadata on the R/3 backend. In addition the Web Dynpro ARFC model itself also caches the metadata. The new invalidation tool will try to refreshes the caches across all the layers. The earlier solution to refresh the caches was to simply restart the engine.

Please look into this Blog, [reimporting a Model without restarting |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df]the J2EE Engine.

Best Regards

Chaitanya.A

[Former Member]

Hi Orlondo,

There is another method by which you dont need to re-start ur J2EE server. Instead of a RFC

re-import, do a fresh RFC import. Create a new model.. import the RFC (wid new structure) into that model. Re-map all the context attributes to this new model node. In the coding also, at many places you would have used the existing model node. Make the changes in all the places.

After this, delete the existing model containing the old RFC structure. But before that you must make sure that other RFCs are not there in that model or else they would also be removed.

After all this, Rebuild your project.

Regards,

Sayan Ghosh

[Former Member]

Hai Orlando,

Its not necessary to restart the j2ee server after reimport of model.Instead of reimport you can clear the cache in the web dynpro console of portal so that the project works fine without restart of j2ee server and the changes are reflected as well.Any issues plz do let me know.

Thanks n Regards

Sharanya.R

Edited by: Sharanya.R on May 30, 2008 6:23 AM

[Former Member]

Hai Oralndo,

Please close the thread if your issue is solved.

Thanks n Regards

Sharanya.R

[Former Member]

hai Orlando,

Wats up?Is your issue fixed or not...Let me know the status as others can follow the same method that i suggested for you instead of restarting j2ee server.

Regards

Sharanya.R

Edited by: Sharanya.R on Jun 2, 2008 9:19 AM

[Former Member]

Clear the caches doesn't work!!

[Former Member]

Hi Orlando,

Whenever u reimport the model server rastart is necessary otherwise the changes will not be reflected. You will get an error when you deploy the application.There is no go around except restarting the server as the meta data gets cached in the server as long as the server is runnig.So, Once you restart the server the cache will be cleared.

Refer to the PDF:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3...

Regards,

Jhansi Miryala