IBM Support

MustGather: WebSphere Application Server Toolkit EJBDeploy problems



Collecting data for problems with the IBM Application Server Toolkit for WebSphere Application Server (Toolkit) EJBDeploy component shipped with the Toolkit and IBM Rational Application Developer. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving The Problem

Tab navigation


EJB Deploy Invocation - The EJB Deployment component takes either a J2EE application containing one or more Enterprise Java™ Beans (EJBs), or a JAR file containing one or more EJBs and generates the necessary deployment code so the WebSphere Application Server can invoke these beans and perform their logic in a transactional environment.

If you have already contacted support, continue on to begin collecting EJBDeploy MustGather data. Otherwise, click: MustGather: Application Server Toolkit.

Collecting EJBDeploy specific information

The EJB Deploy component can be invoked in the following ways:
  1. In a IDE environment, such as the Application Server Toolkit (AST) or Rational Application Developer (RAD).
  2. From the command-line tool ejbdeploy (ejbdeploy.bat / found in the <WebSphere Application Server Install Directory>/bin directory
  3. From the WsEjbDeploy Ant task in WebSphere Application Server (WAS).
  4. From the WAS admin console using the ebdeploy check box (optional). This is not necessary if the ejbdeploy/prepare for deploy has already been generated on the EAR/EJB jar before installing on WAS.

Collect all the information needed to identify the problem fully and recreate it:
  • Since there are four ways to invoke ejbdeploy, identify the method used and all options.
  • Summarize the error.
  • Include screen captures, if appropriate.
  • Include EAR/JAR containing the EJBs with which you are trying to generate deployment code.
  • If using an IDE, errors are recorded in the .metadata/.log file of the workspace, include this .log file.
  • If using batch invocation, redirect console failure information to a text file, and use the -keep command-line flag to prevent the workspace from being removed so you can capture the .metadata/.log information to trace additional errors. Also use the -trace option.
    Submit both of these files.
  • wsejbdeploy also has keepGenerated and trace options that should be used.
  • Execute the following ejbdeploy command using indications 1 - 3:
<WAS_Home>\bin\ejbdeploy.exe <input_ear|input_jar> <tmp_folder> <output_ear|output_jar> -keep -trace -rmic "-keep -verbose" > output_log.txt

1. Manually execute in CLI the above ejbdeploycommand by substituting the parameters in bold with the absolute path values. Note: the WAS_Home is the location of the installation directory of the WAS server.
2. Gather the following files:
  • The output_log.txt file located under the same location where you run the ejbdeploy command.
  • The .log file located in the output._\.metadata folder from the absolute path of the tmp_folder parameter from the ejbdeploy command.
  • The trace file located in absolute path of the tmp_folder from the ejbdeploy command.

3. Zip and upload the files from step 2 along with your input EAR/jar by following instructions in the Exchanging information with IBM Technical Support for problem determination IBM technote.
    You can send this information to IBM Support by using the SR tool, or by FTP.
    If the ejbdeploy failure is in the RAD/AST IDE using Prepare for Deploy, send the information to IBM Support for RAD. If the failure is in ejbdeploy.{bat|sh}, the WsEjbDeploy Ant task or the admin console, send the information to IBM Support for WAS.

    What to do next
    Once you have collected the preceding information you can submit the diagnostic information to IBM support.

    For a listing of all technotes, downloads, and educational materials specific to the EJBdeploy component, search the WebSphere Application Server support site.

    [{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Application Server Toolkit (AST)","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.0;7.0","Edition":"Base","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

    Document Information

    Modified date:
    15 June 2018