User's Manual

Chapter 3: Notes on Interstage Operation
3-18
3) The startup performance of the rapid invocation definition screen of the customize tool that is
started by ejbcustx is improved (V5.0). Because the processing to acquire information on
Enterprise Bean installed when it is listed is accelerated, if Enterprise Bean of the EJB1.1 and
EJB2.0 specification as well as Enterprise Bean of the EJB1.0 specification are installed in the
invoking Bean, they are also listed. If Enterprise Bean of the EJB1.0 specification is selected, an
error message appears, and the edit cannot be performed.
In the same way as for V3.0, in order not to display Enterprise Bean of the EJB1.0 specification on
the rapid invocation definition screen when it is listed, add the -v3 (or -V3) option to the ejbcustx
command and execute it. However, in this case, the processing time remains the same as that for
V3.0.
4) In an environment where screen response is slow (such as when using the customize tool in the
PC X Server), buttons may be operated in succession during the operation of the customize tool
without visible effect. For example, it may take time to mask the button after it is pressed.
The following are specific operations where this behavior may be in evidence:
Multiple dialogs may be opened in these circumstances:
− When you select a button in the definition information (1) panel
− When you select a button on the path settings screen of the WWW browser
− When you select the Change or Add buttons to access environment definition screen
− When you select the Delete
− When you select EJB Application Runtime Environment Definition in the File menu
− When you select Rapid invocation definition in the Tool menu
− When you select DB access environment definition in the Tool menu
− When you select Path settings of the WWW browser in the Help menu
− When you select Version information of the Help menu
If multiple screens or dialogs open, close the unnecessary ones before starting the operation.
When Operating with WorkUnits
1) When operating EJB applications with WorkUnits, do not install the Interstage Java Server Package
and the Interstage package in a folder that includes blank spaces.
2) In the JDK/JRE1.3 environment, if the EJB application is operated in the WorkUnit, do not log off
from Windows NT. When this is done, the JavaVM terminates abnormally due to a JDK1.3 failure
(Bug Id:4323062) and Interstage is forcibly stopped. For more information on JDK1.3 failures, see
the Bug Parade from Sun Microsystems.
Specify without fail –Xrs in the Java Command Option of the WorkUnit definition in case of
JDK1.3.1 environment.