13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

wsadmin scripting<strong>WebSphere</strong> Application Server 5.0 provides a new administration scriptingengine that can be used to manage and deploy applications. Scripts areexecuted under the new tool wsadmin. The wsadmin client uses the BeanScripting Framework (BSF) and is based on JMX.This appendix introduces the scripting language and presents a few simpleexamples that can be customized for different purposes.In <strong>WebSphere</strong> Application Server V4.0, wscp commands were used for bothconfiguration queries and updates, and operational commands. In <strong>V5.0</strong>, adistinction is made between configurational and operational commands.► Configuration functions deal with<strong>WebSphere</strong> Application Server <strong>V5.0</strong>installation and configuration.►Operational functions deal with management of currently running objects in<strong>WebSphere</strong> Application Server <strong>V5.0</strong> installations.Scripts deal with both categories of objects. For example, an application server isdivided into two distinct entities. One entity represents the configuration of theserver, which resides persistently in a repository on permanent storage. You cancreate, query, change, or remove this configuration without starting anapplication server process. The second entity represents the running instance ofan application server by a Java Management Extensions (JMX) MBean. Thisinstance can have attributes that you can interrogate and change, andoperations that you can invoke. These operational actions taken against arunning application server do not have an effect on the persistent configuration ofthe server. The attributes that support manipulation from an MBean differ fromthe attributes the corresponding configuration supports. The configuration caninclude many attributes that you cannot query or set from the live running object.When you run wsadmin in an environment where global security is enabled, youwill need to supply authentication information in order to communicate with theserver. The user’s name and password may be specified either in the commandline arguments for wsadmin or in the sas.client.props file. Changes introducedinto the properties file will depend on whether the RMI or SOAP connector isused to communicate with the server. Remember that if you specify the user’sname and password in the command line, it will override this information in theproperties file.514 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!