Typically the operations are called from the command line on a one by one basis.
A little extra feature admin_client has is the ability to execute a script that contains a set of commands to perform.
Besides enabling scripts to be developed that capture a sequence of related (or common) operations, another benefit of this is that admin_client.jar establishes the connection once, and then executes the commands in the script using the same connection.
A script simply contains the list of admin_client commands to execute, in their normal form.
For example, to stop an application, then perform a redeployment, the script would contain:
-redeploy -file d:\temp\myapp.ear -deploymentName myapp -bindAllWebApps
To execute the script, admin_client.jar is invoked as normal with the deployer_uri and the authentication details, but instead of providing a command to execute you specify the -script option and feed it the script to use.
C:\oc4j\j2ee\home>java -jar admin_client.jar
deployer:oc4j:localhost oc4jadmin welcome1 -script script.txt
06/11/15 20:53:00 Notification ==>Stopping manageable object:
06/11/15 20:53:00 Notification ==>Stop completed for state manageable object:
06/11/15 20:53:01 Notification ==>Uploading file myapp.ear ...
06/11/15 20:53:01 Notification ==>Application Deployer for myapp STARTS.