\n| JDBC<\/td>\n | 2.0<\/td>\n | 2.0<\/td>\n | 3.0<\/td>\n | 3.0<\/td>\n | 3.0<\/td>\n | 4.0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Webserver and Application server<\/strong><\/p>\nWebserver: \u00a0Which hosts websites.<\/p>\n 1)Apache<\/p>\n 2)Microsoft-IIS<\/p>\n 3)Tomcat<\/p>\n 4)Sunone (Iplanet)<\/p>\n 5)IHS (Ibm Http server)<\/p>\n Application server: Which provides run-time environment to support J2EE Applications.<\/p>\n 1)IBM – Websphere<\/p>\n 2)Oracle – Weblogic<\/p>\n 3)JBOSS.<\/p>\n Difference between web server and application server:<\/strong><\/p>\n\n\n\n| \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0 \u00a0 \u00a0\u00a0\u00a0Webserver<\/strong><\/p>\n 1) Which<\/strong>\u00a0hosts websites.<\/p>\n2) Webserver is having web container can \u00a0deploy war files.<\/p>\n 3)webserver can effectively handle static contents.<\/p>\n ex: Serverlet,jsps.<\/p>\n 4) Webserver handles the HTTP protocol. When the Web server receives an HTTP request, it responds with an HTTP response, such as sending back an HTML page.<\/p>\n 5) Web Server serves static HTML pages or gifs, jpegs, etc., and can also run code written in CGI, JSP etc.
\n6) Web Server only supports Servlets and JSP.<\/p>\n <\/td>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Application Server
\n<\/strong><\/p>\n1)Which provides\u00a0run-time\u00a0environment to run J2EE<\/p>\n applications.<\/p>\n 2)Application server is having \u00a0webcontainer as well as Ejb-container can deploy EAR files.<\/p>\n 3)Application server can\u00a0effectively handle dynamic content \u00a0ex: EJB’S<\/p>\n 4)\u00a0Application server is more capable of dynamic behavior than webserver. We can also configure application server to work as a webserver. Simply application server is a superset of webserver.<\/p>\n 5)Application\u00a0<\/strong>Server\u00a0<\/strong>supports\u00a0distributed transaction and EJB.<\/p>\n6)\u00a0An Application Server is used to run business logic or dynamically generated presentation code. It can either be .NET based or J2EE based<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Weblogic server Resources<\/p>\n _________________________________________________________________________________________________________________________<\/p>\n 1) Domain<\/strong><\/p>\n2)Admin Server<\/strong><\/p>\n3)Managed servers<\/strong><\/p>\n4)Cluster<\/strong><\/p>\n5)NodeManager<\/strong><\/p>\n6)Admin console<\/strong><\/p>\n7)JDBC<\/strong><\/p>\n8)JMS<\/strong><\/p>\n9)Virtual hosts<\/strong><\/p>\n10)Security Realms.<\/strong><\/p>\nDomain: A Basic administration unit in weblogic. A group of Logical resources.<\/strong><\/p>\nAdmin server: Which Administrate the hole domain.<\/strong><\/p>\nManages servers: Where actual application are\u00a0deployed. There will one to N number of managed server\u00a0available\u00a0in domain.<\/strong><\/p>\nCluster: Collection of servers that provide fail-over and Load\u00a0balancing\u00a0and\u00a0features\u00a0like scalability and high\u00a0availability.<\/strong><\/p>\nNode Manager:\u00a0<\/strong>NM is a WLS utility that enables you to start\/stop and restart Admin Server and Managed Server instances from a remote location.<\/p>\nAdmin console:\u00a0Administration Console is a Web browser-based, graphical user interface that you use to manage a WebLogic Server domain.<\/p>\n __________________________________________________________________________________________________________<\/p>\n Domain:\u00a0<\/strong>An Oracle WebLogic Server administration domain is a logically related group of Oracle WebLogic Server resources. Domains include a special Oracle WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional Oracle WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web Services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.
\nNode Manager:<\/strong>\u00a0Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.<\/p>\nA Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances\u2014whether Administration Server or Managed Server\u2014that you want to control with Node Manager.<\/p>\n WebLogic Server provides two versions of Node Manager, Java-based and script-based, with similar functionality. However, each version has different configuration and security considerations.<\/p>\n Java-based Node Manager:\u00a0<\/strong>Java-based Node Manager runs within a Java Virtual Machine (JVM) process. It is recommended that you run it as a Windows service on Windows platforms and as an operating system service on UNIX platforms, allowing it to restart automatically when the system is rebooted.<\/p>\nOracle provides native Node Manager Libraries for Windows, Solaris, HP UX, Linux on Intel, Linux on Z-Series, and AIX operating systems.<\/p>\n Note:\u00a0<\/strong>Node Manager is not supported on Open VMS,OS\/390,AS400,UnixWare\/Tru64 UNIX.<\/p>\nScript-based Node Manager:<\/strong>\u00a0For UNIX and Linux systems, WebLogic Server provides a script-based version of Node Manager. This script is based on UNIX shell scripts, but uses SSH for increased security. SSH uses user-id based security.\u00a0For information on configuring the script version of Node Manager, see\u00a0Configuring Script Node Manager<\/a>.<\/p>\n\n\n\n| <\/td>\n | <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n This version does not provide as much security as the Java-based version. However, the advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH. No additional server installation is required. The scripts merely have to be copied to the remote machine.<\/p>\n Note:\u00a0<\/strong>It is recommended that you run script-based Node Manager as Operating System services, which allows to restart automatically when the system is rebooted.<\/p>\n\n\n\n| <\/td>\n | <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Administration Server:<\/strong>\u00a0Admin Server is an instance of Weblogic server. The Administration Server operates as the central control entity for the configuration of the entire domain. It maintains the domain’s configuration documents and distributes changes in the configuration documents to Managed Servers. You can also use the Administration Server as a central location from which to monitor all resources in a domain.<\/p>\nManaged server:\u00a0<\/strong>Apart from Admin Server any weblogic server instance is called Managed server. To prevent the Administration Server from becoming a single point of failure, Managed Servers can always function without the presence a running Administration Server. When a Managed Server starts, it contacts the Administration Server to retrieve its configuration information. If a Managed Server is unable to connect to the specified Administration Server during startup, it can retrieve its configuration directly by reading a copy of the\u00a0config.xml\u00a0file and other files located on the Managed Server’s own file system.<\/p>\nCluster:\u00a0<\/strong>A WebLogic Server cluster consists of multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster\u2019s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.<\/p>\nA cluster is defined as a group of application servers that transparently run a J2EE application as if it were a single entity. \u00a0There are two methods of clustering:\u00a0\u00a0vertical scaling\u00a0<\/strong>and\u00a0horizontal scaling<\/strong><\/p>\nHorizontal clustering:\u00a0<\/strong>It involves running multiple Java application servers that are run on two or more separate physical machines.\u00a0<\/strong>Horizontal scaling is more reliable than vertical scaling, since there are multiple machines involved in the cluster environment, as compared to only one machine.
\nVertical clustering:<\/strong>\u00a0However, consists of multiple Java application servers on a single physical machine.\u00a0With vertical scaling, the machine’s processing power, CPU usage, and JVM heap memory configurations are the main factors in deciding how many server instances should be run on one machine<\/p>\nProxy Server:<\/strong>\u00a0Proxy Server is an intermediary server between your web browser (client) which requests for some information\/data and your server (web server\/Application server) that process the data.<\/p>\nTypes of Proxy Server:<\/strong>\u00a0They are three different types of proxy servers. They are as follows<\/p>\n1) Forward Proxy Servers<\/strong>:\u00a0Forward Proxy Server is a server which forwards the request from the intranet clients (web browser) to the internet servers. These proxy servers are present in the same network of your client.<\/p>\n2) Open Proxy Server:<\/strong>\u00a0An open proxy is a proxy server which is accessible by any Internet user. Any proxy server that doesn\u2019t restrict its client base to its own set of clients and allows any other client to connect to it is known as an \u201cOpen Proxy\u201d. An\u00a0anonymous open proxy\u00a0allows users to conceal their IP address while browsing the Web or using other Internet services. They are in numerous open proxy servers present in Internet. For converting any flavor of proxy servers to Open Proxy servers we just have to enable the flag\u201cProxyRequests On\u201d<\/strong>\u00a0in the configuration file.<\/p>\n3) Reverse Proxy Server:<\/strong>\u00a0A Proxy Server which takes requests from external clients (web browsers) or Internet and forwards them to servers in an internal network is called as Reverse Proxy Server. Generally, the reverse proxy servers are present in the same network where we have our App\/Web servers.<\/p>\nAdvantages of using Reverse Proxy Servers:\u00a0<\/strong>The various advantages of using the proxy servers are as follows:<\/p>\n1)\u00a0\u00a0\u00a0\u00a0\u00a0 Filtering<\/p>\n 2)\u00a0\u00a0\u00a0\u00a0\u00a0 Caching<\/p>\n 3)\u00a0\u00a0\u00a0\u00a0\u00a0 Bypassing filters and censorship<\/p>\n 4)\u00a0\u00a0\u00a0\u00a0\u00a0 Logging and eavesdropping<\/p>\n 5)\u00a0\u00a0\u00a0\u00a0\u00a0 Gateways to private networks<\/p>\n 6)\u00a0\u00a0\u00a0\u00a0\u00a0 Accessing services anonymously<\/p>\n Fire wall:<\/strong>\u00a0It provide filtering, autherization& Authentication services.<\/p>\nIt can act as proxy servers.<\/p>\n Mapping port requests.<\/p>\n Machine:<\/strong>\u00a0A machine is a computer that host WebLogic server.<\/p>\nA machine runs a supported o.s platform.<\/p>\n Can host multiple WebLogic server instances.<\/p>\n WebLogic server Life Cycle:<\/strong><\/p>\n__________________________________________________________________________________________________________<\/p>\n Starting state:<\/strong>\u00a0During the starting state that instances ready the domain configuration data from its configuration directory. Whereas the Manager server will get their configuration data from Admin server. It is in this state that the instance the basic services such as the kernal and execute queues, the container service for logging and Node manager service. The server also deploy during this phase.<\/p>\nStand by:<\/strong>\u00a0In this state the server Instance will allow you to issue just to administrative requests. You can me the server state either running or shutdown state. Normally the server instance will automatically transition through the stand by state to next stage unless you start the instance with the start in stand by command.<\/p>\nNote: All ports are closed in this stat. But you can quickly transition to a running state.<\/p>\n Admin mode:\u00a0<\/strong>The admin mode permits only Administrative task, deploying applications with those applications being able to only request from users with the admin and Apptester roles. Running a server in admin mode is also useful when trying to diagnose problems with application gone badly.<\/p>\nNote: Servers will run in admin mode when there is problem with deployed application or JDBC connection pool.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0–> we can resume the server from Admin state to resume state.<\/p>\n Resuming state: T<\/strong>his is purely transitional\u00a0<\/strong>state the server instance goes through after it transitions automatically through Admin state or you issue the resume command after first placing the instance in the stand by or Admin state. You can do this state change from command line or through the Admin console.<\/p>\nRunning state:\u00a0<\/strong>This is off course final state the server instance reaches after you either issue a startup command or resume command to move the server out of the Admin or stand by state. It is in the running state that the server can accept the service client request for it services.<\/p>\nDifferent between development mode and production mode<\/strong><\/p>\n__________________________________________________________________________________________________________<\/strong><\/p>\n\n\n\n| \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Development mode<\/strong><\/p>\n 1)Auto deployment enabled<\/p>\n 2) The default JDK for development domain is SunHotSopt.(SunJdk)<\/p>\n 3) It is used demo certificate for SSL.<\/p>\n 4) Server instances rotate their log files on startup.<\/p>\n 5) Admin server uses an automatically created boot.properties during startup.<\/p>\n 6) The default maximum capacity for JDBC Date source is 15.<\/p>\n 7) The debug flag which used to start the WebLogic workshop debugger is enabled.<\/td>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Production mode<\/strong><\/p>\n 1)Auto deployment is disabled.<\/p>\n 2) The default JDK for production domain is JRocket.<\/p>\n 3) It is used demo certificate for SSL a warning is displayed.<\/p>\n <\/p>\n 4) Server instances states their log files when it reaches 5Mb<\/p>\n 5) Admin server prompt for username and password during startup.<\/p>\n 6) The default maximum capacity for JDBC Date source is 25.<\/p>\n 7) The debug flag which used to start the WebLogic workshop debugger is disabled.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n WebLogic Installation<\/strong>:<\/p>\n__________________________________________________________________________________________________________<\/p>\n There are 3 types of installations<\/p>\n \n- GUI mode.<\/li>\n
- Console mode.<\/li>\n
- Silent mode.<\/li>\n<\/ol>\n
1) GUI Mode<\/strong>:<\/p>\nStep1: welcome screen<\/p>\n Step2: Accept license agreement.<\/p>\n Step3: Create new BEA home directory<\/p>\n C:\\bea10.3<\/p>\n Step4: Choose installation- Complete (or) Custom<\/p>\n Step5.Select complete<\/p>\n Step6.Select product installation directory<\/p>\n C:\\bea10.3\\wlserver_10.3<\/p>\n 2) Console Mode:<\/strong><\/p>\nserver10.3_win32.exe\u00a0\u00a0-mode = console<\/p>\n 3) Silent Mode:\u00a0<\/strong>\u00a0\u00a0It is a way of setting installation configuration only once and then using those configurations to duplicate the installation on many machines.<\/p>\nThe installation programs read the settings for your configuration from an xml file.(silent.xml)<\/p>\n server10.3_win32.exe -mode=silent -silent.xml=c:\\bea10.3\\silent.xml\u00a0\u00a0-log=c:\\10.3\\silent.log<\/p>\n Step1: Create silent.xml file<\/p>\n <?xml version=”1.0″ encoding=”ISO-8859-1″ ?><\/p>\n <bea-installer><\/p>\n <input-fields><\/p>\n <data-value name=”BEAHOME” value=”C:\\bea10.3″ \/><\/p>\n <data-value name=”USER_INSTALL_DIR” value=”C:\\bea10.3\\wlserver_10.3″ \/><\/p>\n <\/input-fields><\/p>\n <\/bea-installer><\/p>\n Step2: Save this file as silent.xml file in C:\\bea10.3 folder<\/p>\n Step3: Copy the WebLogic software under C:\\bea10.3 folder<\/p>\n Step4: Create a sub folder wlserver_10.3 under c:\\bea10.3<\/p>\n Step5: Execute the below command<\/p>\n server103_win32.exe -mode=silent -silent_xml=C:\\bea10.3\\ silent.xml\u00a0\u00a0-log=C:\\10.3\\silent.log<\/p>\n Domain creation\u00a0<\/strong><\/p>\n__________________________________________________________________________________________________________We can create a domain in 5 types.<\/p>\n <\/p>\n 1)Configuration wizard<\/p>\n 1)GUI<\/p>\n 2)Console<\/p>\n 2)Weblogic server<\/p>\n 3)ANT Task<\/p>\n 4)WLST (Weblogic Scripting tool)<\/p>\n 5)Pack& Unpack.<\/p>\n <\/p>\n Step1:\u00a0<\/strong>Goto the below path and execute config.cmd script<\/p>\nC:\\bea10.3\\wlserver_10.3\\common\\bin>config.cmd<\/p>\n Step2: Select – Create new WebLogic domain<\/p>\n Step3: Select – Base this domain on an existing template<\/p>\n Step4: Configure Administrator username and password.<\/p>\n Step5: Configure server start mode and JDK<\/p>\n Development mode\u00a0\u00a0\u00a0—- SunJdk<\/p>\n Production mode\u00a0\u00a0\u00a0—– Jrocket<\/p>\n Select development mode and SunJdk<\/p>\n Step6: Customize environment & services settings<\/p>\n Select yes if you would like to configure resources<\/p>\n Step7: Configure Admin server<\/p>\n Name : AdminServer<\/p>\n Listen address: localhost<\/p>\n Listen port : 7001<\/p>\n SSL listen:\u00a0\u00a0None<\/p>\n ** Default port number for AdminServer-7001<\/p>\n ** Default ssl listen port : 7002<\/p>\n Step8: Configure managed servers<\/p>\n name\u00a0\u00a0\u00a0\u00a0listen address\u00a0\u00a0\u00a0\u00a0\u00a0listen port\u00a0\u00a0\u00a0ssl listen port<\/p>\n ms1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0localhost\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a07003\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0None<\/p>\n ms2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0localhost\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a07004\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0None<\/p>\n Step9: Configure cluster<\/p>\n Name Multicast address\u00a0\u00a0multicast port\u00a0\u00a0cluster address<\/p>\n c1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0239.192.0.0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a07010\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0localhost:7003, localhost:7004<\/p>\n Step 10: Assign servers to clusters<\/p>\n Step 11: Configure machines<\/p>\n Name\u00a0\u00a0\u00a0Node manager listen address\u00a0\u00a0\u00a0Node manager listenport<\/p>\n m1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0localhost\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a05556<\/p>\n Step 12: Assign servers to machines<\/p>\n Step 13: Create WebLogic domain<\/p>\n Enter the name and location for the domain<\/p>\n Domain name : dev_domain<\/p>\n Domain location : c:\\bea10.3\\user_projects\\domains<\/p>\n Step 14:\u00a0\u00a0Click on\u00a0Create<\/strong><\/p>\n\n- Q) How to start Admin server?<\/strong><\/li>\n<\/ol>\n
C:\\bea10.3\\user_projects\\domains\\dev_domain\\bin>startWebLogic.cmd<\/p>\n \n- Q) How to Access Admin console?<\/strong><\/li>\n<\/ol>\n
http:\/\/localhost:7001\/console<\/p>\n \n- Q) Starting managed servers without node manager?<\/strong><\/li>\n<\/ol>\n
If Adminserver is in another machine:\u00a0<\/strong>c:\\bea\\user_projects\\domains\\webdomain\\bin>startmanagedWebLogic.cmd ms1http:\/\/localhost:7001 (Admin<\/a>\u00a0server port number)<\/p>\nIf Adminserver is in same machine:<\/strong>\u00a0c:\\bea\\user_projects\\domains\\maindomain\\bin>startmanagedWebLogic.cmd ms1<\/p>\n\n- Q) How to stop Admin server?<\/strong><\/li>\n<\/ol>\n
StopWebLogic.cmd\u00a0\u00a0\u00a0—–Windows<\/p>\n StopWebLogic.sh\u00a0\u00a0\u00a0——-Unix<\/p>\n \n- Q) How To stop managed server?<\/strong><\/li>\n<\/ol>\n
StopManagedWebLogic.cmd ms1<\/p>\n \n- Q) How to start Nodemanager?<\/strong><\/li>\n<\/ol>\n
C:\\bea10\\wlserver_10.3\\server\\bin>startNodemanager.cmd<\/p>\n Creating managed servers from console:<\/strong><\/p>\nStep1: Click on Lock& Edit<\/p>\n Step2: Navigate to servers and then click on new<\/p>\n Step3: Create a new server<\/p>\n Step4: Provide server properties<\/p>\n Server name : ms3<\/p>\n Server listen address: localhost<\/p>\n Server listen port: 7005<\/p>\n Step5: Select – this is a stand alone server<\/p>\n Step6: Review choices<\/p>\n Step7: Activate changes<\/p>\n Assigning server to cluster:<\/strong><\/p>\nStep1: Navigate to cluster-cluster name-servers<\/p>\n Step2:\u00a0\u00a0Click on Lock & Edit<\/p>\n Step3:\u00a0\u00a0Add<\/p>\n Add server to cluster<\/p>\n Select existing server and add it as a cluster<\/p>\n Step4: Activate changes<\/p>\n Adding servers to machines:<\/strong><\/p>\nStep1: Navigate to machines-m1-servers<\/p>\n Step2: Lock& Edit<\/p>\n Step3: Add<\/p>\n Step4: Activate changes<\/p>\n How to check Node manager status from console<\/strong>:<\/p>\nWe can\u2019t Start Node manager from console<\/p>\n Step1: Click on machines<\/p>\n Step2: Select m1<\/p>\n Step3: Click on monitoring<\/p>\n Clone<\/em><\/strong>: It creates other server with same properties.<\/em><\/p>\nwe can clone servers machines and clusters.<\/em><\/p>\nwe should not cluster managed server while the server is running.<\/em><\/p>\n–>boot.properties-it contains username and password<\/em><\/p>\n–>Development mode-automatically creates boot.properties file<\/em><\/p>\n–> Production mode-we have to create boot.properties file.<\/em><\/p>\n–> setDomainEnv -we can change the mode from development to production or production to development modedoing changes in this file.<\/em><\/p>\nDeployments<\/p>\n __________________________________________________________________________________________________________<\/p>\n <\/p>\n Several methods are available to deploy the Oracle WebLogic Server applications and shared libraries, including:<\/p>\n \n- Administration console<\/li>\n
- WebLogic Scripting Tool(WLST)<\/li>\n
- WebLogic.Deployer java class<\/li>\n
- wldeploy Ant task<\/li>\n
- Auto-deployment folder<\/li>\n<\/ol>\n
Deployment an application involves the following tasks:<\/strong><\/p>\nPreparing:\u00a0\u00a0<\/strong>Choosing weather to package the application as an archived file or keep in an exploded directory.<\/p>\nConfiguring:\u00a0<\/strong>Creating a deployment plan to maintain the configuration changes without changes the deployment descriptors.<\/p>\nDeploying:\u00a0<\/strong>Targeting and distributing the application to servers in an OracleWebLogicServer domain.<\/p>\nDeploment Methods:<\/strong>\u00a0WLS (WebLogic scripting) supports three types of deployment methods.<\/p>\n\n- Auto-deployment<\/li>\n
- Console deployment<\/li>\n
- Command-line Deployment<\/li>\n<\/ol>\n
You can deploy:<\/strong><\/p>\n\n- Enterprise, Web, and EJB applications<\/li>\n
- Web services<\/li>\n
- J2EE libraries<\/li>\n
- JDBC, JMS and Diagnostic Framework modules<\/li>\n
- Resource adapters<\/li>\n
- Optional packages<\/li>\n
- Client application archives<\/li>\n<\/ol>\n
Applications and EJBs can be deployed:<\/strong><\/p>\n\n- In an archived file(.ear, .war, .jar)<\/li>\n
- In an exploded(open)directory format<\/li>\n<\/ol>\n
Archive Files:\u00a0<\/strong>There are three archive files to deployed in Oracle WebLogic Server.<\/p>\n1)\u00a0JAR(Java Archive):<\/strong>\u00a0Jar is java archive file. It contains all class file, image, sound and other files which will needed in whole application. Computer users can create or extract JAR files using the jar command that comes with the JDK. They can also use zip tools. The JavaTM Archive (JAR) file format enables you to bundle multiple files into a single archive file. jar was designed mainly to facilitate the packaging of java applets or applications into a single archive.<\/p>\nCreating Jar File:<\/strong><\/p>\njar\u00a0\u00a0-cvf\u00a0\u00a0\u00a0filename.jar \u201c.\u201d<\/p>\n Extracting Jar file:<\/strong><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>Jar\u00a0\u00a0\u00a0-xvf\u00a0\u00a0<\/strong>filename.jar<\/p>\n2) WAR(web Archive):\u00a0<\/strong>Web Archive (WAR) file is a Java archive file used to store jsp, servlets, classes, meta data information, images and Sound and tag libraries etc. It is standard file extension is .war. WAR files are used to package Web modules. A WAR file is for a Web application deployed to a servlet\/jsp engine.<\/p>\nCreating war File:<\/strong><\/p>\njar\u00a0\u00a0-cvf\u00a0\u00a0\u00a0filename.war \u201c.\u201d<\/p>\n Extracting Jar file:<\/strong><\/p>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>jar\u00a0\u00a0\u00a0-xvf\u00a0\u00a0<\/strong>filename.war<\/p>\n | | | | | | |