Hi,
Step 1) Download Websphere Installer from the official IBM Site
http://www.ibm.com/developerworks/downloads/ws/was/
There are two types of installers, BASE Edition and Network Deployment.Only Base Edition is available for trail. We can only create standalone servers with that.Network Deployment Installer comes with additional fetaures like Clustering. You can check the official Website for more details.
Step 2) Extract the installer
tar -pxvzf was.cd.7007.trial.base.opt.linux.ia32.tar.gz
Step 3) Create a responsefile.base.txt with the following content.
-OPT allowNonRootSilentInstall=”true”
-OPT disableOSPrereqChecking=”true”
-OPT disableNonBlockingPrereqChecking=”true”
-OPT installType=”installNew”
-OPT feature=”noFeature”
-OPT installLocation=”/home/apps/ebsi/fkmd/WAS/AppServer”
-OPT PROF_enableAdminSecurity=”true”
-OPT PROF_adminUserName=wasadmin
-OPT PROF_adminPassword=wasadmin
-OPT PROF_profileName=AppSrv01
-OPT PROF_hostName=localhost
-OPT PROF_nodeName=node01 -
-OPT PROF_defaultPorts=”true”
-OPT traceLevel=INFO
Step 4) Install with the following options
./install –options responsefile.base.txt -silent
Check the following location to verify that the installation went fine.
user_home/waslogs
Normally it takes 10-15 minutes for the installation.
Step 5) Start the Server
$ pwd
/WAS/AppServer/bin
$ ./startServer.sh server1
ADMU0116I: Tool information is being logged in file
/WAS/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 30162
Step 6) Access the console with credentials wasadmin/wasadmin
https://localhost:9043/ibm/console
Thanks
Faisal Khan



August 2nd, 2010 on 10:28 pm
hi jay
plz tell me detail about log files.
how many types of log files are there and which are most imp log files in weblogic?
may wht is the location of stdout and stderr log files?
thnks in advance…
thanks
venu
August 2nd, 2010 on 10:52 pm
Hi Venu,
Basically there are 3 types of Log files which we require to analyze any Server related issues. All the 3 kind of Log files can be found in “<DOMAIN_HOME>\servers\<SERVER_NAME>\logs” directory (Which is the default location for these files). But in most of the production environments we change the Log File Locations to wherever we want.
1). Access Logs: These Log files tells us the details of each and every Http Request which is made to the Server. The Byte data/Data/time/request resource/host/client IP addresses…etc.
2). Server Logs: Tells us about the Activities happening on the Server. This logs are filled up by the WebLogic Server Codes…and somethimes it is also possible that the application also can write inside the WebLogic Server Logs by using “servletContext.log(String)” methos. But that is not a best proctice to allow an Application to write data inside the WebLogic Server Logs. The Server Logs becomes more important when we enable the Debug flags on the Server to deepely analyze different issues…because the debug/info/warning/critical/error…etc messages goes inside the Server Log.
3). Out Log: This files usually writes the JVM activity and System.out.println(String) data inside it. Whenever we enable some JVM parameters (independent of Server) like -verbose:gc (to get Garbage collection details). kind of flags these Details goes inside the Stdout Logs. Whenever we use “Kill -3 <PID>” or ctrl+break utilities to collect the THREAD DUMPS …it also goes inside the Server out files. We can write the STDOUT and STDERROR messages to any file we want using the following JAVA_OPTIONS:
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.Stdout=”any-stdout-filename” (you can define your File location as well in the file path-name)
-Dweblogic.Stderr=”any-stderr-filename”
If you donot want to have a separete Stdout file then you can redirect the Data of your OUT file inside the Server Log using the following Flag:
-Dweblogic.log.RedirectStdoutToServerLogEnabled=true
4). NodeManager Logs: These logs provides us the information about NodeManager Activities. NodeManager Debugs also comes in this Log. You can find these Logs inside “<WL_HOME>\common\nodemanager\logs” directory.
.
.
Keep Posting
Thanks
Jay SenSharma
August 3rd, 2010 on 8:26 pm
Hi Faisal Khan,
I am trying to deploy the code in WLS9.2 by using the script. We are using external stage mode, the path is /domain/servers/ser-1/stage/eintel/.ear. I have created directory stage, eintel manually. The script will copy the code to the destination by using ftp. It is showing
WebLogic/apps/eintel923/eintel923Domain/servers/eintel91/stage/eintel/eintel.ear
7188056 bytes sent in 0.2 seconds (35868.74 Kbytes/s)
221-You have transferred 7188056 bytes in 1 files.
221-Total traffic for this session was 7188630 bytes in 1 transfers
After copying it will call the script containing weblogic.Deployer. Here I am getting the error as follows and the dirs eintel and the code also getting deleted automatically.
starting deployment ….
weblogic.Deployer invoked with options: -adminurl 10.177.107.16:7001 -user weblogic -name eintel -external_stage -source /WebLogic/apps/eintel923/applications/eintel/deploymentSource/eintel.ear -deploy -targets eintel9Cluster
Task 16 initiated: [Deployer:149026]deploy application eintel on eintel9Cluster.
Task 16 failed: [Deployer:149026]deploy application eintel on eintel9Cluster.
Target state: deploy failed on Cluster eintel9Cluster
Could not start email servlet: Could not load property bundle eintel_default
08/03/10 09:04:51 – EIProperties.loadProperties CAUSE: java.util.MissingResourceException: Can’t find bundle for base name eintel_default, locale en
Could not start email servlet: Could not load property bundle eintel_default
08/03/10 09:04:51 – EIProperties.loadProperties CAUSE: java.util.MissingResourceException: Can’t find bundle for base name eintel_default, locale en
August 3rd, 2010 on 8:52 pm
Hi Guys,
This issue is environment specific. For this issue I added one cmdline argument
“-Dcom.mot.corp.GISEnvironment=TEST” and restarted the servers. Again I did the deployment from there everything is working fine.
Thanks
Prasad Kasthuri