When you first start an Application Server Toolkit (AST), Rational Web Developer or Rational Application Developer (RAD) assembly tool, menu choices for the J2EE Perspective might not be enabled. To assemble code artifacts into J2EE modules that can be deployed onto an application server, you must work in the J2EE Perspective. This article explains how to configure your assembly tool for work on J2EE modules and specify a target server supported by WebSphere Application Server.
Before you begin
Before you can configure an assembly tool, you must install and start the assembly tool.Why and when to perform this task
Configuring an assembly tool consists of ensuring that menu choices for the J2EE Perspective are enabled and specifying a target server supported by WebSphere Application Server. When you first start an assembly tool, menu choices for the J2EE Perspective might not be enabled, meaning that you cannot assemble code artifacts into deployable J2EE modules. You perform the steps in this article when you cannot work in the J2EE Perspective or when you need to specify a new target server for your modules.Steps for this task
What to do next
When you configure a J2EE module, select a target server for the module from the list of available target servers.To change the list of available target servers, click Window > Preferences > Server > Installed Runtimes to go to the Installed Server Runtime Environments section of the Preferences dialog. Use the Add, Edit, Remove or Search options to change the list of target servers as needed.
To change the target server for a module, right-click on the module in the Project Explorer view and click Properties > Server. Change the value for Target runtime to select a different target server for the module. In the assembly tools, the terms target server and target runtime have the same meaning.
Related tasks
Assembling applications