The scripting library provides Jython script procedures to assist in automating your
environment. Use the application management scripts to install, uninstall, export, start, stop, and
manage business-level applications in your environment.
About this task
스크립트 라이브러리는 가장 일반적인 애플리케이션 서버
관리 기능을 자동화하는 프로시저 세트를 제공합니다. Jython 스크립트 라이브러리를
사용하는 방법에는 다음 세 가지가 있습니다.
- wsadmin 도구를 사용하여 대화식 모드에서 Jython 스크립트 라이브러리의
스크립트를 실행합니다. wsadmin 도구를 실행한 후 다음 구문을 사용하여
스크립트 라이브러리에 포함된 개별 스크립트를 실행할 수 있습니다.
wsadmin>AdminServerManagement.createApplicationServer("myNode", "myServer", "default")
- 문서 편집기를 사용하여 다음 샘플에 표시된 것과 같이 Jython 스크립트
라이브러리의 여러 스크립트를 결합합니다.
#
# My Custom Jython Script - file.py
#
AdminServerManagement.createApplicationServer("myNode", "Server1", "default")
AdminServerManagement.createApplicationServer("myNode", "Server2", "default")
# Use one of them as the first member of a cluster
AdminClusterManagement.createClusterWithFirstMember("myCluster", "APPLICATION_SERVER", "myNode", "Server1")
# Add a second member to the cluster
AdminClusterManagement.createClusterMember("myCluster", "myNode", "Server3")
# Install an application
AdminApplication.installAppWithClusterOption("DefaultApplication",
"..\installableApps\DefaultApplication.ear", "myCluster")
# Start all servers and applications on the node
AdminServerManagement.startAllServers("myNode")
사용자 정의
스크립트를 저장한 후 다음 구문 데모에 표시된 것과 같이 명령행에서 이
스크립트를 실행합니다. bin>wsadmin -language jython -f path/to/your/jython/file.py
- 샘플 구문과 같이 Jython 스크립트 라이브러리 코드를 사용하여 사용자
정의 스크립트를 작성합니다. 스크립트 라이브러리의 각 스크립트 예제는
wsadmin 스크립트를 작성하는 우수 사례를 보여 줍니다. 스크립트 라이브러리 코드는
app_server_root/scriptLibraries 디렉토리에 있습니다.
이 디렉토리에서 스크립트는 기능에 따라 서브디렉토리로
구성됩니다. 예를 들어, app_server_root/scriptLibraries/application/V70 서브디렉토리에는
버전 7.0 이상 제품에 적용 가능한 애플리케이션 관리 태스크를 수행하는 프로시저가 있습니다.스크립트
라이브러리 경로의 서브디렉토리 V70은 해당 서브디렉토리의
스크립트가 버전 7.0 스크립트임을 의미하지 않습니다.
The business-level application procedures in scripting library are located in the
app_server_root/scriptLibraries/application/V70
subdirectory. Each script from the directory automatically loads when you launch the wsadmin tool.
To automatically load your own Jython scripts (*.py) when the wsadmin tool starts, create a new
subdirectory and save existing automation scripts under the
app_server_root/scriptLibraries directory.
우수 사례: To
create custom scripts using the scripting library procedures, save the modified scripts to a new
subdirectory to avoid overwriting the library. Do not edit the script procedures in the scripting
library.
bprac
You can use the AdminBLA.py scripts to perform multiple combinations of administration functions.
See the business-level application configuration scripts documentation to view argument descriptions
and syntax examples.
Use following steps and the scripting library to create an empty business-level application, add
assets as composition units, and start the business-level application.
Procedure
- Launch the wsadmin tool.
Use this step to launch the wsadmin tool and connect to a server, or run the tool in local mode.
If you launch the wsadmin tool, use the interactive mode examples to run scripts.
When the wsadmin tool launches, the system loads all scripts from the scripting
library.
- Import assets to your configuration.
Assets represent application binaries that contain business logic that runs on the target run
time environment and serves client requests. An asset can contain a file, an archive of files such
as a ZIP or Java™ archive (JAR) file, or an archive of archive files such as a Java Platform, Enterprise Edition
(Java EE) EAR file. Other examples of assets include Enterprise JavaBeans (EJB) JAR files, EAR
files, OSGi bundles, mediation JAR files, shared library JAR files, and non-Java EE contents such as
PHP applications.
Run the importAsset script from the AdminBLA script library to import assets to the application
server configuration repository, as the following example
demonstrates:
bin>wsadmin -lang jython -c "AdminBLA.importAsset("asset.zip", "true", "true")"
You can also use interactive mode to run the script procedure, as the following example
demonstrates:
wsadmin>AdminBLA.importAsset("asset.zip", "true", "true")
- Create an empty business-level application.
Run the createEmptyBLA script from the AdminBLA script library to create a new business-level
application, as the following example
demonstrates:
bin>wsadmin -lang jython -c "AdminBLA.createEmptyBLA("myBLA", "bla to control transactions")"
You can also use interactive mode to run the script procedure, as the following example
demonstrates:
wsadmin>AdminBLA.createEmptyBLA("myBLA", "bla to control transactions")
- Add the assets, as composition units, to the business-level application.
Composition units can represent deployed assets, other business-level applications, or external
artifacts that are deployed on non-WebSphere Application Server runtime
environments without backing assets. Business-level applications contain zero or more composition
units. You cannot add the same composition unit to more than one business-level application, but you
can use one asset to create more than one composition unit.
Run the addCompUnit script from the AdminBLA script library to add asset.zip to myBLA as a
composition unit, as the following example
demonstrates:
bin>wsadmin -lang jython -c "AdminBLA.addCompUnit("myBLA", "asset.zip", "default",
"myCompositionUnit", "cu description", "1", "server1", "specname=actplan1")"
You can also use interactive mode to run the script procedure, as the following example
demonstrates:
wsadmin>AdminBLA.addCompUnit("myBLA", "asset.zip", "default", "myCompositionUnit",
"cu description", "1", "server1", "specname=actplan1")
- Save the configuration changes.
다음 명령 예제를 사용하여 구성 변경사항을 저장하십시오.
AdminConfig.save()
- Synchronize the node.
Use the syncActiveNodes script in the AdminNodeManagement script library to synchronize each
active node in your environment, as the following example
demonstrates:
wsadmin>AdminNodeManagement.syncActiveNodes()
- Start the business-level application.
Use the startBLA script from the AdminBLA script library to start each composition unit of the
business-level application on the deployment targets for which the composition units are configured,
as the following example
demonstrates:
wsadmin>AdminBLA.startBLA("myBLA")
Results
The business-level application is configured and started on the deployment target of
interest.
The wsadmin script libraries return the same output as the associated wsadmin commands. For
example, the AdminServerManagement.listServers() script returns a list of available servers. The
AdminClusterManagement.checkIfClusterExists() script returns a value of true if the
cluster exists, or false if the cluster does not exist. If the command does not
return the expected output, the script libraries return a 1 value when the script successfully runs.
If the script fails, the script libraries return a -1 value and an error message with the
exception.
By default, the system disables failonerror option. To enable this option, specify
true as the last argument for the script procedure, as the following example
displays:
wsadmin>AdminApplication.startApplicationOnCluster("myApplication","myCluster","true")
What to do next
Use the business-level application configuration scripts to create custom scripts to automate
your environment. Save custom scripts to a new subdirectory of the app_server_root/scriptLibraries directory.