Hi All
Please note this is to deploy to the production environment, so all tools must be available by default on a Window 2003 Server.
The .msi files has been created by the build process. The production deployment team is now asking for more automation and improvement. Here are the steps I see from the deployment instruction document (I put it here to give more info):
. Remove <product> web service in Add/Remove Programs
. Check if ceartain components have been removed from the Component Services.
.
Execute the <product>.msi (user complains about no status provided during the installation, what shall I do to add that? )
. Create some folder in C:\Temp, and grand permission to some users
. Ensure installed <product> is using ASP.Net 2.0
. Configure <product> to using particular application pool in IIS 6.
. Configure <product> web site directory security to use a particular identity.
And also there are BizTalk installations:
. Export current binding
. Stop integration orchestration
. Unenlist integrations
. Undeploy and unbinding
. remove integration
. deploy
....
The deployment team is also asking to provide
1. The .msi file with an "Answer File" so the deployment can be done unattended, and
2. A batch file to automate the above steps.
Which type of scripting you normally use for this job? WScript? VBScript?
Thanks a lot.
Jirong
