WeblogicInstallGuide-12c

Oracle WebLogic Server 12c Installation Guide Updated February 28, 2014

Table of Contents

Contents 1.

Overview ....................................................................................................................................................... 3

2.

Install WebLogic 12c .................................................................................................................................... 4

3.

Configure WebLogic .................................................................................................................................. 20

4.

Configure WebLogic Licensing.................................................................................................................. 23

5.

Configure Logging ...................................................................................................................................... 24 Configure Java Logging .................................................................................................................................................................................... 24 Configure WebLogic Oasis Domain Logging ............................................................................................................................................... 25 Configure WebLogic Server Logging ............................................................................................................................................................. 26 Configure WebLogic HTTP Logging.............................................................................................................................................................. 27

6.

Configure WebLogic Security .................................................................................................................... 28

7.

Configure JDBC.......................................................................................................................................... 33

8.

Configure SSL ............................................................................................................................................ 40 Generate Private keys ........................................................................................................................................................................................ 40 Generate the Certificate Request (CSR).......................................................................................................................................................... 41 Import the Certificate from a trusted CA ........................................................................................................................................................ 41 Configure WebLogic to use the new keystore (private key & certificate) ................................................................................................ 41 Configure WebLogic to enable only 128 bit SSL Encryption ..................................................................................................................... 44

9.

Web.xml Additional Information................................................................................................................ 45

10.

Install Web Config Tool ............................................................................................................................. 46 Required WebLogic Groups for the Web Config Tool................................................................................................................................. 47 Required Oasis Profiles for the Web Config Tool......................................................................................................................................... 47 External Dependencies ...................................................................................................................................................................................... 47 Deploy Web Config Workbench ...................................................................................................................................................................... 47

11.

Appendix A Customer Web App Questionnaire ........................................................................................ 48

12.

Appendix B Allocating Additional Memory for the Managed Server ....................................................... 49

THE INFORMATION CONTAINED HEREIN IS CONFIDENTIAL AND PRIVILEGED AND MAY ONLY BE DISCLOSED OR DISTRIBUTED WITHIN DELPHI TECHNOLOGY INC. AND ONLY TO THOSE PERSONS ESTABLISHING A NEED-TO-KNOW. ANY OTHER DISCLOSURE HEREOF IS STRICTLY PROHIBITED.

1. Overview 1. Assure OASIS database is up to latest revision. 2. Customer sets up server and configures firewall. Customer opens appropriate ports to internet and corporate network if required: •

port 80 for http

•

port 443 for ssl

•

3rd port for admin console (default is 7001)

3. Customer provides information for SSL Certificate if required: •

common name (services.customer.com for example)

•

org unit

•

org

•

city

•

state

•

country code

•

encryption strength (1024 domestic or 512 exportable)

4. Acquire necessary components •

Acquire WebLogic 12c (12.1) from Oracle’s Weblogic site o Be sure to download the Generic Installer (for use with 64bit JVMs) o The file will be a .jar

•

Acquire Java SE Development Kit 6u38 for Windows x64 from Oracle’s Java site. o Be sure to download the Windows x64 installer

•

Upgrades from previous versions of WebLogic (8.1 and 10 MP1) are not supported.

Delphi requires that the application is installed in the exact location listed in the documentation. If you choose to install in a different location, Delphi will not be able to provide adequate technical support.


2. Install WebLogic 12c 1. Run the Java JDK1.6.0_38 64bit installer (jdk-6u38-windows-x64.exe).

2. Make the install path E:\Oracle\Middleware\ THE INFORMATION CONTAINED HEREIN IS CONFIDENTIAL AND PRIVILEGED AND MAY ONLY BE DISCLOSED OR DISTRIBUTED WITHIN DELPHI TECHNOLOGY INC. AND ONLY TO THOSE PERSONS ESTABLISHING A NEED-TO-KNOW. ANY OTHER DISCLOSURE HEREOF IS STRICTLY PROHIBITED.

3. Click “Next.” and wait for install to finish.

4. Go to “Start” in the search box type: “CMD” then right click the result and select “Run as Administrator”

5. Change the working directory to the location you have your wls1211_generic.jar saved


6. Install WebLogic 12c on server by running “wls1211_generic.jar” using the JDK you just installed. The Weblogic install wizard will then launch:

7. Click “Next.”


8. Click “Create a new Middleware Home” and provide a home directory (E:\Oracle\Middleware) then click “Next.”

9. Fill out the form if you have an Oracle Support account or uncheck the box if you do not want to receive Security updates.


10. Choose “Custom” then “Next”

11. Uncheck “Oracle Coherence” and click “Next.”


12. Click “Next” on JDK Selection.

E:


13. Accept the default and click “Next.”

14. Select “No” and click “Next”


15. Select “All Users” and click “Next”


16. View the installation summary and click “Next.”

17. Click on your start menu -> All Programs -> Oracle Enterprise Pack for Eclipse -> WebLogic Server 12c -> Tools -> Configuration Wizard.


18. Click “Create a new WebLogic configuration” then click “Next.”

19. Choose the default “Generate a domain configured automatically to support the following products” then click “Next.”


20. Change the domain name from “base_domain” to “oasis” and click “Next.”

21. Change the user name from “weblogic” to “admin”; provide passwords then click “Next.” Write the passwords down on your checklist!


22. Choose “Development mode” and select the latest Sun SDK (SDK 1.6.0_18 in the example above). Click “Next.”

23. Check both boxes to modify Administration Server and Managed Server, Clusters and Machines settings and click “Next”.


24. Check the “SSL enabled” checkbox. SSL listen port: 7443. Click “Next.”

25. Click “Add” to create a managed server. Change the name from “new_ManagedServer_1” to “Managed1,” Change Listen port to “80,” enable SSL and set it to port 443.


26. Click “Next” to bypass configuring a cluster.

27. Click “Add” to create a machine to run the “managed server” and name it, “localhost.” Change the Node manager listed port to 5555


28. Select the servers on the left and click the arrow to the right so they will be managed by the “localhost” machine that was just created.

29. Click “Next.”


30. Review your WebLogic domain configuration and click “Create.”

31. When progress is 100%, just click “Done.”


3. Configure WebLogic 1. Create a directory to hold all WebLogic data (installed applications and logs). o Create a directory called “e:\wldata”. o Create a directory called “e:\wldata\logs”. o Create a directory called “e:\wldata\apps”. 2. Now with these assumptions in mind: o Installed WebLogic into a WebLogic Home called “e:\Oracle\Middleware” o Created the domain “oasis” and used AdminServer and Managed1 for your Weblogic server names •

In order to install WebLogic Server as a Windows service you must install it manually – see instructions below. WebLogic will have created a directory called E:\Oracle\Middleware\wlserver_10.3\server\bin. A file called “installSvc.cmd” can be found in that directory. Make a copy of it as well as “uninstallSvc.cmd” from that same directory and copy them to E:\Oracle\Middleware\user_projects\domains\oasis. Open “installSvc.cmd” in a text editor.

•

Add the following variables before call "%WL_HOME%\common\bin\commEnv.cmd" @rem Set JAVA_VENDOR to java virtual machine you want to run on server side. set JAVA_VENDOR=Sun @rem Set JAVA_HOME to java virtual machine you want to run on server side. set JAVA_HOME=E:\Oracle\Middleware\jdk160_38 @rem USERDOMAIN_HOME is preset to the domain directory. set USERDOMAIN_HOME=E:\Oracle\Middleware\user_projects\domains\oasis @rem Set SERVER_NAME to the name of the server you wish to start up. set SERVER_NAME=AdminServer @rem Set DOMAIN_NAME to the name of the server you wish to start up. set DOMAIN_NAME=oasis

•

Find “"%WL_HOME%\server\bin\beasvc" -install” and add the portion highlighted in bold (all on one line)


"%WL_HOME%\server\bin\beasvc" -install -svcname:"beasvc %DOMAIN_NAME%_%SERVER_NAME%" -delay:60000 -javahome:"%JAVA_HOME%" execdir:"%USERDOMAIN_HOME%" -extrapath:"%EXTRAPATH%" -password:"%WLS_PW%" cmdline:%CMDLINE% -log:"e:\wldata\logs\AdminServer\stdout.log" •

Go to the command prompt (start/run, type cmd.exe). Switch to the directory e:\oracle\Middleware\user_projects\domains\oasis.

•

Type the following: installsvc admin password

Replace password with the administrative password you created when installing WebLogic. The WebLogic Windows service will be installed. •

To install the Managed server as a windows service, make a copy of installSvc.cmd and name it “installSvcManaged.cmd” Add the following variables before call "%WL_HOME%\common\bin\commEnv.cmd" @rem Set JAVA_VENDOR to java virtual machine you want to run on server side. set JAVA_VENDOR=Sun @rem Set JAVA_HOME to java virtual machine you want to run on server side. set JAVA_HOME=E:\Oracle\Middleware\jdk160_38 @rem USERDOMAIN_HOME is preset to the domain directory. set USERDOMAIN_HOME=E:\Oracle\Middleware\user_projects\domains\oasis @rem Set WLS_USER equal to your system username and WLS_PW equal @rem to your system password for no username and password prompt @rem during server startup. Both are required to bypass the startup @rem prompt. set WLS_USER=YourAdminUsername set WLS_PW=YourAdminPassword @rem Set SERVER_NAME to the name of the server you wish to start up. set SERVER_NAME=Managed1 @rem URL of the Admin Server


set ADMIN_URL=http://LOCALHOST:7001 @rem Set DOMAIN_NAME to the name of the server you wish to start up. set DOMAIN_NAME=oasis •

Find “"%WL_HOME%\server\bin\beasvc" -install” and add the portion highlighted in bold (all on one line) "%WL_HOME%\server\bin\beasvc" -install -svcname:"beasvc %DOMAIN_NAME%_%SERVER_NAME%" -depend:"beasvc oasis_AdminServer" javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" extrapath:"%EXTRAPATH%" -password:"%WLS_PW%" -cmdline:%CMDLINE% log:"e:\wldata\logs\Managed1\stdout.log" (The line may wrap)


4. Configure WebLogic Licensing Oracle Weblogic 12c and higher do not require the installation of a license key. Sign in to WebLogic Console: 1. Start the WebLogic service. In Windows Services, the service will be called “beasvc oasis_AdminServer”. 2. Log in to the WebLogic console which will be accessible via port 7001 by default. The url to be used is http://localhost:7001/console but only from the local server desktop. If server is accessible remotely, you can replace “Localhost” with the Hostname, IP Address, or Fully Qualified Domain Name (FQDN) of the server. To login, use the userid “admin” and password used when the domain was configured.


5. Configure Logging Assuming WebLogic is installed in E:\Oracle\Middleware, and that the JDK selected for the “oasis” domain was JDK 1.6.0_38. The first step is to enable and configure standard Java logging for all Oasis web applications.

Configure Java Logging 1. In Windows Explorer, browse to the directory E:\Oracle\Middleware\jdk160_38\jre\lib and open the file “logging.properties” in a text editor. 2. Comment out the line (# is a comment): handlers= java.util.logging.ConsoleHandler 3. Remove the comment from the line (remove the #) #handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler 4. Find the lines below and make the changes in bold java.util.logging.FileHandler.pattern = e:/wldata/logs/java%u.%g.log java.util.logging.FileHandler.limit = 500000 java.util.logging.FileHandler.level = ALL java.util.logging.FileHandler.count = 100 java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter 5. Restart the WebLogic Admin Server and Managed Windows Services.


Configure WebLogic Oasis Domain Logging 1. Return to the WebLogic console. 2. Assuming you named the domain “Oasis”, click on “Oasis” at the top of the left navigation menu. 3. Click on the “Configuration” tab in the first row and the “Logging” tab in the second row:

4. For “Log File Name:”, type “e:\wldata\logs\oasis.log”. 5. For “Rotation Type”, select “By Time” 6. For “Begin Rotation Time”, enter “00:00” 7. For “Rotation interval”, enter “24” hours. 8. Check “Limit Number of Retained Log Files.” 9. For “Files to Retain”, type 14 (this will retain 2 weeks of logs. Adjust as necessary). 10. Check “Rotate log file on startup.” 11. Click “Save.”


Configure WebLogic Server Logging 1. In the WebLogic console, expand “Environment,” and then “Servers” in the left navigation menu and click “AdminServer”. 2. Click on the “Logging” tab in the first row and “General” in the second row.

3. For “Log File Name”, type “e:\wldata\logs\AdminServer\AdminServer.log” where “AdminServer” is the name of your Admin server. 4. For “Rotation Type”, select “By Time” 5. For “Begin Rotation Time”, enter “00:00” 6. For “Rotation interval”, enter “24” hours. 7. Check “Limit Number of Retained Log Files.” 8. For “Files to Retain”, type 14 (this will retain 2 weeks of logs. Adjust as necessary). 9. Check “Rotate log file on startup.” 10. Click “Save.” 11. Repeat steps for the “Managed1” server, and set the “Log File Name” to “e:\wldata\logs\Managed1\Managed1.log” where “Managed1” is the name of your managed server.


Configure WebLogic HTTP Logging 1. In the WebLogic console, expand “Servers” in the left navigation menu and click “AdminServer”. 2. Click on the “Logging” tab in the first row and “HTTP” in the second row.

3. For “Log File Name”, type “E:\WLData\Logs\AdminServer\access.log” 4. For “Rotation Type”, select “By Time” 5. For “Begin Rotation Time”, enter “00:00” 6. For “Rotation interval”, enter “24” hours. 7. Check “Limit Number of Retained Log Files.” 8. For “Files to Retain”, type 14 (this will retain 2 weeks of logs. Adjust as necessary). 9. Check “Rotate log file on startup” and click “Save.” 10. Repeat steps for the “Managed1” server and set the “Log File Name” to “e:\wldata\logs\Managed1\access.log” where “Managed1” is the name of your Managed server. 11. When finished with the log configurations, click “Save.


6. Configure WebLogic Security 1. Make sure the WebLogic Windows service is running. 2. Log in to the WebLogic console using whichever port was set. If port 7001, then use the following link. http://localhost:7001/console. To login, use the userid “admin” and password used when the domain was configured. 3. To set the minimum password length, on the left navigation menu, expand “Security Realms” → “myrealm” → “Providers” → “Authentication” → “Default Authenticator”. Click “Configuration” and then “Provider Specific”.

The minimum password length is 8, but can be changed per Organization’s requirements. WebLogic services may need to be restarted for this change to take effect. 4. To set user lockout policy, click on “Security Realms” on the left navigation menu then “myrealm.” Click the “User Lockout” tab.


Password lockout policies can be changed per Organization’s requirements. WebLogic services may need to be restarted for this change to take effect.


5. To create the necessary WebLogic Security Groups, navigate to “Users and Groups” by clicking “Security Realms” on the left navigation menu, then “myrealm”. Groups may be application specific.

6. Click “New” to configure a new group.

7. Provide values for the group and description and click “OK”.


8. To create the necessary users in WebLogic, click “Users” underneath the “Users and Groups” tab. These userids should match users found in the OASIS table pfuser. The web_user_b flag on that table should be set to ‘Y’.

9. Click “New” to configure a new user.


10. Enter the userid in the “Name” field and provide a description (first and last name is good) and password. Click “OK,” then click the new User ID you created and click the “Groups” tab.

11. Add the necessary groups and click “Save”.


7. Configure JDBC 1. Make sure the “Managed” server is running. Scroll down to System Status and see that there is a number (2). Click on the link for “OK” and verify the following screen.

2. Verify the state of both servers is “RUNNING” and that the health is “OK.”

3. Note that the WebLogic console can also be accessed via HTTPS – e.g. https://localhost:7443/console. If you have not configured SSL with a valid SSL Certificate yet (see configure SSL from the table of contents), you will see a dialog box appear informing you that the certificate is not trusted. Simply click “Continue to this website (not recommended)” to proceed.


4. On the left navigation menu, expand “Services” then “JDBC” then “Data Sources.” Click “Lock & Edit” to add a new Data Source.


5. Click “New” to configure a new JDBC Data source.

6. Select “Oracle” as the database type and then click “Next”.


7. Select Oracle’s Driver (Thin) for Instance connection; Versions: 9.0.1,9.2.0,10,11 and click “Next”.

8. Leave the next values as default to support Global transactions, and using One-Phase Commit.


9. Enter the values for your Oracle database server. Use the table below to gather the database information. Name

Oasis

Database Name

Oracle SID – get from DBA

Host Name

Host name or IP Address of Oracle Server

Port

Listener port of database (often 1521 or 1526) – get from DBA

Database User Name

Userid – get from DBA

Password

user’s password – get from DBA

Confirm Password

password again


10. Click “Test Configuration” to ensure the pool is configured correctly. If it fails, please verify your connection information and that your Weblogic server can communicate with your Database server over the port specified for Oracle. Click “Next.”

11. Select the managed server to deploy the new JDBC Data Source, then click “Finish.”

12. The next screen will list out a Summary of your JDBC Data Sources.


13. Click on “oasis,” click the “Configuration” tab, then click “Connection Pool,” scroll down and click “Advanced”.

14. Click “Test Connections on Reserve and then click “Save.”

15. Scroll down to find “Connection Creation Retry Frequency” and set to 900 seconds (15 minutes)


8. Configure SSL Follow these steps if you are deploying the application in an environment requiring SSL encryption (HTTPS). It assumes WebLogic is installed in E:\Oracle\Middleware. The Sun provided “keytool” command which is part of the JDK will be used. Note: The SSL port must be enabled when WebLogic was configured. If not, please do that now before proceeding.

Generate Private keys If you are expecting domestic encryption (1024 bit) then you will use a keysize or 1024, otherwise use 512. 1. Open a DOS shell and switch to E:\bea\wlserver_10.0\server\bin. 2. Set the PATH to include the Java executables: SET PATH=e:\bea\jdk150_11\bin;%PATH%

3. Generate the private keys as follows (keysize is 1024 for domestic encryption, change to 512 for exportable encryption) keytool –genkey –alias oasis –keysize 1024 –keyalg RSA –keystore e:\bea\wlserver_10.0\server\lib\oasis.jks

4. Provide answers to the questions (some of which must come from the customer) as follows: Enter keystore password:

Provide a password but write it down!

What is your first name and last name?

This is the common name and you will provide the URL, such as services.delphitech.com.

What is the name of your organizational unit?

Customer Provided – Ex. Information Services

What is the name of your organization?

Customer Provided – Ex. Customer Name, Inc.

What is the name of your City or Locality?

Customer Provided – Ex. San Francisco

What is the name of your State or Province?

Customer Provided – Ex. California

What is the two-letter country code for this unit?

Customer Provided – Ex. US

Is […..] correct?

Verify and then type yes if it is correct.

Enter key password for

Press enter.

(RETURN if same as keystore password):


Generate the Certificate Request (CSR) 1. Open a DOS shell and switch to E:\bea\wlserver_10.0\server\bin. 2. Set the PATH to include the Java executables: SET PATH= e:\bea\jdk150_11\bin;%PATH%

3. Generate the Cert Request (CSR file) as follows: keytool –certreq –file oasis.csr –alias oasis –keystore e:\oracle\middleware\wlserver_10.3\server\lib\oasis.jks

When prompted, provide the password you used when generating the private key.

Import the Certificate from a trusted CA 1. Open a DOS shell and switch to e:\oracle\middleware\wlserver_10.3\server\bin. 2. Set the PATH to include the Java executables: SET PATH= e:\oracle\middleware\jdk160_38\bin;%PATH%

3. Copy your certificate file (.cer) to E:\Oracle\Middleware\jdk160_38\bin. 4. Import the Certificate (.cer file) as follows: keytool –import –trustcacerts –file certfile.cer –alias oasis –keystore e:\oracle\middleware\wlserver_10.3\server\lib\oasis.jks

When prompted, provide the password you used when generating the private key. Confirm the certificate. NOTE: The certificate file should be a PKCS#7 formatted file!

Configure WebLogic to use the new keystore (private key & certificate) 1. In a web browser start the WebLogic console and log in. 2. On the left navigation menu, expand the “Servers” node and click on “Managed1”. 3. Click on the “Keystores” tab. Click the “Change” button next to “Demo Identity and Demo Trust”


4. Assuming the certificate authority is a standard one, such as Thawte or verisign, select “Custom Identity and Java Standard Trust”, otherwise select “Custom Identity and Custom Trust”. Click “Continue”. If using “Custom Identity and Java Standard Trust”

5. Enter the keystore filename e:\oracle\middleware\wlserver_10.3\server\lib\oasis.jks. Enter “JKS” for key store type and then provide the password you used for the passwords. Click “Continue”


If using “Custom Identity and Custom Trust”

6. For both the Custom Identity and Custom Trust, enter the keystore filename e:\oracle\middleware\wlserver_10.3\server\lib\oasis.jks. Enter “JKS” for key store type and then provide the password you used for the passwords. Click “Save”.


7. Click on the SSL tab and enter “oasis” for the private key alias then provide the passwords and click “Save”.

Configure WebLogic to enable only 128 bit SSL Encryption 1. Open the file “config.xml” in WordPad. The file can be found in e:\bea\user_projects\domains\oasis. 2. Find the element called “SSL” (example below – it may not match exactly):

3. Insert the following attributes into this XML element: Ciphersuites="SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_3DES_EDE_CBC_SHA"

4. The resulting xml should look something like this:


9. Web.xml Additional Information 1. Add the following info to use updatepassword.jsp. updatepassword updatepassword.jsp admin

2. Add the following info to use createuser.jsp. createuser createuser.jsp admin

3. Add the following info to use maintainusers.jsp. maintainusers maintainusers.jsp admin

4. Add the following info to use forgotpassword.jsp. forgotpassword forgotpassword.jsp admin


10.Install Web Config Tool 1. Create a directory called “e:\wldata\apps\WebWB”. 2. Unzip the webmaint.zip file into the e:\wldata\apps\WebWB directory. Make sure you “use folder names” 3. Edit the e:\wldata\apps\WebWB\web-inf\web.xml file and make sure the only entry is as follows: Oracle Datasource jdbc/oasis javax.sql.DataSource Container

4. Update the following as follows: dbPoolId jdbc/oasis java.lang.String

5. If the tool will be used over SSL, uncomment out the two entries:

and this entry

6. Set the number of days before a password expires by changing the for passwordExpDays. Use zero for no requirement. passwordExpDays 30 java.lang.String

7. Set the number of days of inactivity before a userid is locked by changing the for inactivityLockDays. Use zero for no locking. inactivityLockDays 0 java.lang.String


Required WebLogic Groups for the Web Config Tool These groups should be created in WebLogic to support the tool. EMPLOYEE – for employees

Required Oasis Profiles for the Web Config Tool Superusers should have the WEB_DTI_ADMIN profile as this gives them full access to all menuitems in WebWB.

External Dependencies There are no external dependencies for this tool.

Deploy Web Config Workbench 1. Return to the WebLogic Console. 2. Expand “Deployments” in the left navigation menu and click on “Web Application Modules”. 3. On the main page, click “Deploy a new Web Application Module…”. 4. Next to “Location”, click the link for “E:”, then the link for “wldata”, then the link for “apps”. 5. Check the radio button next to “WebWB” then click the “Target Module” button. 6. Next, click the “Deploy” button.


11. Appendix A Customer Web App Questionnaire This information should be provided by a Delphi customer in order to proceed with the installation of a web applications. Required Information Method of connecting to the Server where WebLogic and Web Application is to be installed (for example: Proxy Master or VPN, etc…) The above Web Server IP Address The Web Server Login and Password (Need Admin User ID and Password) Where on this Web server should the files be stored (Need to confirm the directory structure, for example; e:\ ) *Oracle Database IP address that the Web Application will be accessing (for setting JDBC connection pool)) *Oracle SID *Oracle Schema User ID and Password *Oasis User ID (user ID has to exist in Oasis/PFUSER table) to access the Web Application(s) Note: WebLogic user will need to be created to be exactly the same as this oasis user ID, but password can be different.

Note: To redirect the Web Application to access different database, the information with (*) is needed on the new database to… 1) Setup a new JDBC connection pool. 2) Setup a new JDBC Data Source 3) Setup a new Web User ID


12.Appendix B Allocating Additional Memory for the Managed Server 1. Once the Managed Server has been installed as a Windows service, you can adjust the amount of memory allocated to the Managed Server by modifying the registry entry associated with the windows service. 2. Start by opening “regedit” from a command prompt. Administrative rights to the registry are required to make changes. 3. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLS oasis_Managed1\Parameters

4. Double click “CmdLine” and make the following edits to “-client -Xms32m -Xmx200m XX:MaxPermSize=128m”

5. Change the minimum memory (-Xms) allocated to the WLS Java process to 4096, and the maximum memory (-Xmx) to 4096 as well. Change the MaxPermSize to 1024. 6. Change the –client to –server to run the Sun Java JDK for the Managed1 server in “Server” mode. The value data for start of the CmdLine string should look like this: -server –Xms4096m –Xmx4096m -XX:MaxPermSize=1024m 7. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\beasvc oasis_AdminServer\Parameters 8. Change the minimum memory (-Xms) allocated to the WLS Java process to 512, and the maximum memory (-Xmx) to 768 as well. Change the MaxPermSize to 256. 9. Change the –client to –server to run the Sun Java JDK for the AdminServer in “Server” mode. THE INFORMATION CONTAINED HEREIN IS CONFIDENTIAL AND PRIVILEGED AND MAY ONLY BE DISCLOSED OR DISTRIBUTED WITHIN DELPHI TECHNOLOGY INC. AND ONLY TO THOSE PERSONS ESTABLISHING A NEED-TO-KNOW. ANY OTHER DISCLOSURE HEREOF IS STRICTLY PROHIBITED.

The value data for start of the CmdLine string should look like this: -server –Xms512m –Xmx768m -XX:MaxPermSize=256m 10. Click OK and close the registry editor. 11. Restart the WebLogic services from the windows services console.


WeblogicInstallGuide-12c

Recommend Documents