WEBLOGIC SERVER

1. WEBLOGIC SERVER SETUP AND CONFIGURATIONS

2. GETTING STARTED • Weblogic Installation • Creating domain through configuration wizard • Creating domain using existing template • Creating servers

3. Creating Weblogic Domain • Go to the path D:\BEA923\weblogic92\common\bin in your installation and run the script config.cmd. • A GUI is displayed which allows you to either create a new domain or to extend an existing domain, check Create a new weblogic domain and click on next:

4. - You can either generate a new domain with new configurations (which is the first option) or you can create the domain using the existing domain. We see the first option right now. Check the option Workshop for weblogic platform if workshop is required. Click on next.

5. - Enter the username and password as weblogic, and the same thing in confirm password and click on next. - Select of you want to run the server in development mode or production mode. Also select which jdk do you want to use for all the servers in this domain, is it sun jdk or Oracle JRockit. Both are bundled with the WLS installation. You can also use any other jdk and give the path in other jdk. Click on next.

6. - Next will be the screen of customizing the configurations of the servers, adding a cluster etc. If you check no, it will not allow you to change the configurations at the time of domain creation, but this can be done later, so it is not mandatory to check yes and change the settings now. When yes it checked, it allows you to change the port of admin server, create managed servers, create machine, clusters, assign managed servers to the machine and cluster, all at the time of domain creation itself. Click on next.

7. - The next screen will be the domain name, which you can change, and the domain home, this will be the directory where all the configuration files etc will be saved on your system. - You can change that as per your preference, but right now we will use the default path in the installation. -The next screen will show you process of domain creation. Once the process is 100% complete, you can check Start Admin Server and click on done to start the admin server directly.

8. Creating a Domain Template - Run the script config_builder.cmd from the path D:\BEA923\weblogic92\common\bin A GUI will be displayed which has 2 options, check Create a domain template .

9. - Select the correct domain from the path of which you are creating a template: (Security_domain in the image) Click on next. - Just give the name of the template in the next screen, everything else is optional.

10. - In the next screen you get an option to add other files in the domain template. Click on the file on the left, select the destination on the right and click on add, the file will be copied. Click on next on the Add SQL Scripts as it is choosing the database for your domain, we will use the default one.

11. - Change the admin server IP address or port as needed and click on next. - You can create additional users and groups in the template, but it is not mandatory, check no and click on next. - Next screen says specify start menu entries, which means in the start menu you will see scripts like startWeblogic.cmd etc which is like a shortcut to start the server. Click next.

12. - The next screen gives an option of replacing variables, for example you click on startWeblogic.cmd it can be edited by clicking on edit. Click next. Next screen shows the overview of the template which will be created.

13. - On the next screen, give the name of the template and the location where you would like to save it. Default location is D:\BEA923\user_templates in your installation. - When you click on finish, progress of the template creation is seen and the location where the template is created will be displayed.

14. Domain Configuration using Template - Run the configuration wizard which you used to create a new domain. Check Create a new domain and click on next. - Now check the option Base this domain on an existing template and give the location of the template which you created before: Click next.

15. - Let the username and password be the same. - Now choose either development mode or production, and choose the jdk to be used as done before. - Follow the same steps which were followed to create a new domain before and see that the domain is created with the configurations of another domain.

16. Creating Servers • When you create a domain, an admin server is created. • - Start the admin server with the script startWebLogic.cmd in the directory D:\BEA923\user_projects\domains\base_domain\bin • You will see the server transitioning from the state starting -> standby-> starting ->admin -> resuming -> running. • Open the admin console using the url http://<listenAddress>:<listenPort>/console • - For example : http://localhost:7001/console

17. Question: Why do we need to create managed servers when we already have a admin server? Answer: The admin server allows you to deploy the applications and it works absolutely fine. But we create managed servers for advantages like load-balancing and failover between the servers, and admin server cannot participate in these features. We will discuss in detail in the topic of clusters. To create a managed server, expand Environments on the left side of the screen, click on Servers.

18. Now click on Lock and Edit. Without clicking this button, you cannot create or modify anything. Basically it means that you are locking the console while you are making any changes to the domain, which indicates that no other user can modify anything in the domain when you are doing it. Click on New

19. The next screen will ask for details of the managed server. Give the name. The listen address will be your system’s IP. Give the server port different from what is given for the admin server. The combination of listen address and port number should be unique for each server. Also, the listen address in the screen shot is given 7003 and not 7002 because 7002 is a reserved port for the SSL communication of admin server. For now, check the option No, this is a stand-alone server. Click on next.

20. Next screen will show you the details of the managed server. If you want to change anything, click on back, else click finish, and the server will be created. To make the changes take effect, click on activate changes which now took place of lock and edit. Note: To check if there are changes pending, click on the link View changes and restarts which is above the lock and edit button. Act accordingly.

21. To start the managed server, run the script startManagedWebLogic.cmd from the directory D:\BEA923\user_projects\domains\base_domain\bin through the command prompt as below: D:\BEA923\user_projects\domains\base_domain\bin>startManagedWebLogic.cmd ManagedServer1 (We specify the name of the managed server we need to start after the script) When you are starting the server, it will ask you for the username and password, provide the username and password given for the admin server (weblogic, weblogic) From the admin console when you go to managed server 1 -> configurations -> general tab, you can see the detailed parameters. You can modify the listen address, port of the server, can assign the server to the cluster, machine. SSL can be enabled. The parameters which have a yellow exclamation mark indicate that the server would need a restart for the changes to take effect if any of them are modified.

22. Other important tabs: • Protocols: To modify the communication protocols used by the server. Enable tunneling is always recommended for proper communication • Logging: To alter the name, type and severity of the domain logs, server logs, and out file. • Debug: To enable debug flags for the server to retrieve extra internal information which normally is not shown in the log files. • Monitoring: It will give the state of the server, jdk and OS it uses, and other information. • Control: Will be used when the server is associated with a machine and nodemanager is used to control the server. • Deployments: Show the current targeted deployments on the server • Services: Shows the datasources, workmanagers, and other resources targeted to the server. (We will see that in detail later.) • -Security: To define roles and policies for the managed server. (We will see that in detail later)