The scripting library provides Jython script procedures
to assist in automating your environment. Use the scripts in the AdminResources
script library to configure mail, URL, and resource settings.
Before you begin
Before you can complete this task, you must install an application
server 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
resource management procedures in scripting library are located in
a
app_server_root/scriptLibraries/resources/ 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 AdminResources.py scripts
to perform multiple combinations of administration functions. See
the documentation for the resource configuration scripts for additional
scripts, argument descriptions, and syntax examples.
The example
script configures a custom mail provider and session. A mail provider
encapsulates a collection of protocol providers like SMTP, IMAP and
POP3, while mail sessions authenticate users and controls users' access
to messaging systems. Configure your own mail providers and sessions
to customize how JavaMail is handled.
Procedure
- Optional: Launch the wsadmin tool.
Use
this step to launch the wsadmin tool and connect to a server, job
manager, or administrative agent profile, 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.
- Create a mail provider.
Run the createMailProvider
script from the AdminResources script library, specifying the node
name, server name, and new mail provider name, as the following example
demonstrates:
wsadmin -lang jython -c "AdminResources.createMailProvider(myNode, myServer, newMailProvider)"
You
can also use interactive mode to run the script procedure, as the
following example demonstrates:
wsadmin>AdminResources.createMailProvider(nodeName, serverName, mailProviderName)
- Define the protocol provider for the mail provider.
You can also configure custom properties, classes, JNDI name,
and other mail settings with this script. See the documentation for
the resource configuration scripts for argument descriptions and syntax
examples. Run the configMailProvider script from the AdminResources
script library to define the protocol provider, as the following example
demonstrates:
wsadmin -lang jython -c "AdminResources.configMailProvider(myNode, myServer, newMailProvider, "", "", "SOAP", "", "", "", "", "", "")"
You can also use interactive mode to run the script
procedure, as the following example demonstrates:
wsadmin>AdminResources.configMailProvider(myNode, myServer, newMailProvider, "", "", "SOAP", "", "", "", "", "", "")
- Create the mail session.
Run the createMailSession
script from the AdminResources script library, specifying the node
name, server name, mail provider name, mail session name, and Java™ Naming and Directory Interface (JNDI) name
arguments, as the following example demonstrates:
wsadmin -lang jython -c "AdminResources.createMailSession("myNode", "myServer", "newMailProvider", "myMailSession", "myMailSession/jndi")"
You
can also use interactive mode to run the script procedure, as the
following example demonstrates:
wsadmin>AdminResources.createMailSession("myNode", "myServer", "newMailProvider", "myMailSession", "myMailSession/jndi")
- Save the configuration changes.
다음 명령 예제를 사용하여 구성 변경사항을 저장하십시오.
AdminConfig.save()
- Synchronize the node.
To propagate the configuration
changes to the node, run the syncNode script procedure from the AdminNodeManagement
script library, specifying the node of interest, as the following
example demonstrates:
wsadmin -lang jython -c "AdminNodeManagement.syncNode("myNode")"
You
can also use interactive mode to run the script procedure, as the
following example displays:
wsadmin>AdminNodeManagement.syncNode("myNode")
Results
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
Create custom scripts to automate your environment by
combining script procedures from the scripting library. Save custom
scripts to a new subdirectory of the app_server_root/scriptLibraries directory.