如何在WebSphere 8.5.5上脚本部署每日生成的静态HTML页面？

Hey there! Let me walk you through how to automate this static HTML deployment workflow in WebSphere 8.5.5, since you’re used to the simpler JBoss approach. I’ll cover two practical methods that fit your daily update needs:

WebSphere’s wsadmin tool is your go-to for command-line automation. This method works great if you want to either update just the new static files or redeploy the full war/ear package.

Step 1: Copy New Static Files Directly to the Deployed App Directory #

If your app is configured to allow runtime updates, you can skip repackaging the war entirely. WebSphere keeps an expanded version of your deployed app here (adjust paths for your environment):

# Example Linux path
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWeb.war/

Use a simple copy command to add your daily HTML files:

cp /path/to/daily-generated-html/* /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/MyCell/MyApp.ear/MyWeb.war/static-content/

Pro tip: Make sure you enabled "Allow file updates at runtime" when deploying the app (check the application options in the WebSphere console). If you did, WebSphere will automatically detect and load the new files without a restart.

Step 2: Use wsadmin to Trigger Updates/Redeploys #

If direct file copies don’t trigger a refresh, or you need to redeploy the full war, write a Jython script (WebSphere’s default scripting language) to handle it. Here’s a sample update_app.py:

# Connect to the WebSphere server
AdminControl.connect()

# Define your app details
app_name = "MyWebApp"
updated_war_path = "/path/to/updated/MyWeb.war"

# Option 1: Update only the web module with new content
AdminApp.update(app_name, "app", ["-operation", "update", "-contents", updated_war_path])

# Option 2: Full redeploy (uninstall then reinstall)
# AdminApp.uninstall(app_name)
# AdminApp.install(updated_war_path, ["-appname", app_name, "-contextroot", "/myweb"])

# Save configuration changes
AdminConfig.save()

# Start the app if you did a full redeploy
# AdminControl.invoke(AdminControl.queryNames('WebSphere:type=Application,name='+app_name+',*'), 'start')

Run the script with wsadmin:

/opt/IBM/WebSphere/AppServer/bin/wsadmin.sh -lang jython -f update_app.py

(Use .bat instead of .sh for Windows environments.)

If you prefer the "drop files and go" approach like JBoss’s .dodeploy, WebSphere has a built-in auto-deploy feature.

Step 1: Enable Auto-Deploy in the Console #

1. Log into the WebSphere admin console
2. For a standalone server: Go to Servers > Server Types > WebSphere Application Servers > [Your Server] > Auto Deployment
3. For a deployment manager: Go to System Administration > Deployment Manager > Auto Deployment
4. Check "Enable auto deployment", set a monitoring directory (e.g., /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/autodeploy), and set a polling interval (60 seconds works for daily updates)
5. Save changes and restart the server if prompted

Step 2: Automate War Updates & Copy to the Monitored Directory #

Daily, update your war with new HTML files and drop it into the auto-deploy directory. WebSphere will pick it up and deploy automatically:

# Update the war with new HTML files
jar uf /path/to/MyWeb.war /daily-generated-html/*.html

# Copy to WebSphere's auto-deploy directory
cp /path/to/MyWeb.war /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/autodeploy/

If you’re using an ear package, replace the war inside the ear first before copying the ear to the auto-deploy directory.

• Permissions: Ensure the WebSphere runtime user has read/write access to the app’s expanded directory or auto-deploy folder.
• Runtime Updates: Always enable "Allow file updates at runtime" during app deployment to avoid unnecessary restarts when adding static files.
• Script Variables: Make your scripts maintainable by defining paths and app names as variables (e.g., WAS_PROFILE="/opt/IBM/WebSphere/AppServer/profiles/AppSrv01").

内容的提问来源于stack exchange，提问作者Tom CLERC