Hi , Is there any installation tool for installing ear application in the websphere console ? Like by clicking setup.exe , the process leads to the installation of ear application the websphere console by using any tool ?? My client need the application to be installed by himself. Can any one please help me to solve this..........
hi siva you can make use of the SEAppinstall.bat file in the bin directory if u r using the WAS4.0 Single Server Edition. but if u r using the WAS4.0 Multi Server Edition u can write a TCL script(Tool Control Language) and use it with the wscp(WebSphere Console Program) to deploy the ear. u can find the wscp.bat in the bin directory of the Multi Server Edition. for writing the TCL script u can look into the redbooks or the infocenter hope this helps
Thanks<br /> <br />Kiran <br /> <br />SCEA, SCJP 1.4,<br /> <br />"First they ignore u, then they laugh at u, then they fight u, <br />then u will win<br /> <br />Mahatma Gandhi"
Joined: Apr 04, 2002
Hi kiran , Can you plz. tell some more details reg. tcl script and ear installation please If u give an example I will be more happy
Joined: May 18, 2001
hi siva this is the sample TCL script what is given in the infocenter for installing the sampleApp.ear available in the installableApps directory of the WebSphere Server
set mynode xxxxx set instdir i:/WebSphere/AppServer/installableApps/ set earfile sampleApp.ear set sname "Default Server" set jdbcdrivername "Sample DB Driver" set datasourcename SampleDataSource1 set vhostName "default_host" set db2implclass COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource set db2zipfile e:/SQLLIB/java/db2java.zip set dbname WAS set dbuser xxxxx set dbpassword xxxxx # create prerequiste objects # # first, the JDBCDriver set implclassattr [list ImplClass $db2implclass] set descriptionattr [list Description "Sample JDBC Driver build by wscp"] set attributelist [list $implclassattr $descriptionattr] JDBCDriver create /JDBCDriver:$jdbcdrivername/ -attribute $attributelist # next, install the driver JDBCDriver install /JDBCDriver:$jdbcdrivername/ -node /Node:$mynode/ -jarFile $db2zipfile # now create the datasource # set databasenameattr [list DatabaseName $dbname] set defaultuserattr [list DefaultUser $dbuser] set defaultpasswordattr [list DefaultPassword $dbpassword] set descriptionattr [list Description "Sample DataSource build by wscp"] set attributelist [list $databasenameattr $defaultuserattr $defaultpasswordattr $descriptionattr] DataSource create /JDBCDriver:$jdbcdrivername/DataSource:$datasourcename/ -attribute $attributelist # and the virtual host set aliaslist [list *:80 *:9080] set aliasattr [list AliasList $aliaslist] set attributelist [list $aliasattr]
VirtualHost create /VirtualHost:$vhostName/ -attribute $attributelist # Now install the application # # construct -ejbdatasources option set ejbsource1 [list Increment.jar /JDBCDriver:$jdbcdrivername/DataSource:$datasourcename/] # Note - the syntax of this will change with defect 105059 -- the new syntax will be the # following, to make it consistent with other commands #set ejbsource1 [list Increment.jar jdbc/$datasourcename] set ejbsources [list $ejbsource1] # construct -cmpdatasources option set cmpsource1 [list Increment.jar::Inc jdbc/$datasourcename] set cmpsources [list $cmpsource1] # Note: This one could have -modvirtualhosts and -ejbreferences and -ejbnames * If the user wanted to modify them EnterpriseApp install /Node:$mynode/ $instdir$earfile -defappserver /Node:$mynode/ApplicationServer:$sname/ -ejbdatasources $ejbsources -cmpdatasources $cmpsources
you can get a full description of it in the infocenter itself. you can even go through the site
or you can get more info in the site www.developer.ibm.com if you have already created all the resources like the DataBase Drivers, Datasource etc that your application needs you can only make use of the install of the ear file block in the TCL script.
hope this helps [ May 23, 2002: Message edited by: kiran sonata ]
Hi, As well as WSCP you can use the XmlConfig utility provided with WAS4.0 AE (not sure if its included with single server edition). We've used this in the following manner. First you manually setup the application server, virtual host, and resources. Then you install the ear file using the wizard. Then export the congifuration to an XML file. In my experience you setup the application server manually at least once at the start of development - so this isn't as much pain as you think it is. Therefore, for subsequent installs you simply ensure that the deployed ear file is in the installable apps directory and run the XmlConfig utility against your exported XML file. The beauty of this approach is that the XmlConfig picks up your ear file and installs it. Then you can create a server group and clones if you require a clustered environment. You can include substitution variables in the XML files so that you can specify various parameters, such as the node to install to, at run time. I hope this helps. Cheers, Steve