You can use the server tools views to manage servers.
The following tasks may be included as part of the development path:
Adding projects to a server
Once you have created a server, you need to create
a relationship between the projects that contain the files you want to test
and your server.
Starting a server
When you are ready to test your
projects, you must start a server. In some situations, listed below,
the server tools start a server for you automatically. For more information
on which test server will start, refer to the list of related topics
at the end of this topic.
Clean projects published on the server
You can use the clean option available in the Servers
view to remove any invalid resources from the server before doing a full republish.
This helps remove by-products generated as a result of the publishing process.
When you find there is old code or an invalid state of code running on the
server, try using this clean option to see if this helps remove these invalid
states from the server.
Setting a default server
A default server is the server that you
want to use when a project has more than one server defined.
Generating WebSphere administrative commands to assist in developing Jython scripts
Use the WebSphere® Administration Command assist tool to generate WebSphere administrative (wsadmin) commands
for Jython scripting language as you interact with the WebSphere Administrative Console. When
you perform server operations in the WebSphere Administrative Console, the WebSphere Administration Command
assist tool captures and displays the wsadmin commands issued. You
can transfer the output from the WebSphere Administration Command view directly to a text editor,
such as the Jython editor, enabling you to develop Jython scripts
based on actual console actions.
Accessing the Administrative Console
You can use the advanced functions provided in the administrative
console to change settings in your server configuration.
Backing up server configuration from a WebSphere Application Server
The Server Configuration Backup wizard packages the server's
cell configuration files into a configuration archive (.car) file.
The configuration archive file contains files under the x:/profile/config/cells directory, where x:/profile is the directory of your profile for the WebSphere Application Server.
If you are familiar with wsadmin commands, this wizard performs the
same functionality as the wsadmin method exportWasprofile in the AdminTask object.
Restoring server configuration to a WebSphere Application Server
The Server Configuration Restore wizard applies the server
configuration that is defined in the configuration archive file (.car)
to the server profile associated to the selected server in the Servers
view. The profile's original port numbers, host name and WebSphere Application Server installation
directory are preserved. However, all other server configuration settings
on your current profile are merged with the server configuration that
is defined in the selected configuration archive file, in a manner
that maintains the differences. If you are familiar with the WebSphere administrative scripting
(wsadmin) commands, this wizard performs the same functionality as
the wsadmin method importWasprofile in the AdminTask object.
Migrating server configuration files from an earlier to a later version of WebSphere Application Server
The Server Configuration Backup and Server Configuration
Restore options available in the workbench are not the correct
way to migrate a profile from an earlier to a later version of WebSphere Application Server.
The server is going to fail to start if you attempt to restore the
server configuration of an earlier version of WebSphere Application Server into a later
version. Instead, you should use the Migration wizard from the later
version of WebSphere Application
Server to migrate server configuration files from an earlier version
of the server.
Running administrative script files on a WebSphere Application Server
You can run administrative scripts from within the development
environment, without having to switch to the non-graphical command
interpreter, WebSphere Application Server wsadmin tool. Use the WebSphere®
Application Server Administrative Script Launcher to run administrative
script files on WebSphere Application Server. To run script files
within the development environment you need to specify the location
of your script, the runtime environment to interpret your script,
and the security settings; if your script is running against a secured
server.