Q
Problem solve Get help with specific problems with your technologies, process and projects.

Keeping the J2EE engine from starting automatically

The J2EE engine is interfering with cluster operations. Expert Austin Sincock rides to the rescue.

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.
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 last published in July 2003

Dig Deeper on SAP Java and J2EE

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close