This preview shows page 427 - 429 out of 672 pages.
profile creation. If this option is chosen during profile creation, a prompt to provide a user ID and password is displayed. The user ID and password are stored in a set of XML files and are mapped to the administrator role. More users can be added after profile creation by using the administrative tools.
402WebSphere Application Server V8.5 Concepts, Planning, and Design Guide12.3 Administration facilities of WebSphere Application ServerWebSphere Application Server V8.5 provides these administrative tools to configure and manage your runtime environment:The administrative consoleThe administrative console is a browser-based client that uses a web application that runs in the web container to administer WebSphere Application Server. WebSphere scripting client (wsadmin)The wsadminclient is a non-graphical scripting interface that administers WebSphere Application Server from a command-line prompt. It can connect to WebSphere Application Server by using one of the two communication mechanisms:–SOAP by communicating with the embedded HTTP server in the web container–Remote Method Invocation (RMI) to communicate with the administrative servicesTask automation with Apache AntApache Ant is used to create build scripts that compile, package, install, and test applications on WebSphere Application Server. Administrative programmingYou can develop custom Java applications that use the Java Management Extensions (JMX) based on the WebSphere application programming interface (API).Command-line utilities WebSphere Application Server provides administrative utilities to help manage your environment. It includes the following features:–Called from a command line–Can be used to run common administrative tasks such as starting and stopping WebSphere Application Server and backing up the configuration–Work on local servers and nodes only, including the deployment managerThe combination of administrative tools that you employ ultimately depends on the size and complexity of your runtime environment. If you have few resources but many tasks, consider using automation and scripts. If you have multiple administrators who perform different tasks, consider defining different access control roles. The use of different access control roles is important where you want non-administrators to perform limited roles such as application deployment. Updates to configuration through the administrative console or the wsadminclient are kept in a private temporary area called a workspace. The changes are not copied to the configuration repository until an explicit save command is issued. The workspace is in the profile_root\wstempdirectory. By using a workspace, multiple clients can access the configuration concurrently. Use care to prevent change conflicts. Clients can detect such conflicts and allow you to handle them. For example, the wsadminclient has a property called setSaveModethat can be set to control the default save behavior if a conflict occurs.
You've reached the end of your free preview.
Want to read all 672 pages?
Wind, Web server, IBM WebSphere Application Server, IBM WebSphere, IBM Software, IBM WebSphere Application Server Community Edition