Keeping the J2EE engine from starting automatically

Keeping the J2EE engine from starting automatically

What is the best way to prohibit the J2EE engine on your central instance of Web AS 6.20 to start? We have several dialog instances which we intend to run a SAP J2EE cluster on, but we do not want the central instance to partake in cluster operations. I have found it very difficult configuring the cluster without the first instance of the J2EE on the central instance.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

In Web AS 6.20, the J2EE engine must be configured through parameters. It can also be manually stopped and started through the Internet Communications Manager transaction (SMICM). You will probably want to set the profile parameters in RZ10 and RZ11. Check out the rdisp/j2ee* parameters. Setting rdisp/j2ee_start to false will disable the J2EE engine on startup. Make sure you have the blessing of your BASIS people before making any changes to the profile parameters.

This was first published in July 2003