Oracle Webcenter Framework Portal Application has provided facilities to make a control over home page that you want to show once the user has accessed the Portal Framework Application URL and to which pages login and logout actions should lead.
The Oracle Webcenter Portal Framework Application that will be resulted in by end of this practice will be deployed on Oracle Managed Server (WC_CustomPortal) instance that will be created by using Oracle Portal Template through an extension of your domain.
In the previous tutorials you had deployed your Oracle Webcenter Portal Framework Application into either Oracle Webcenter WC_Spaces instance or on the JDeveloper Integrated Managed Server.
While deploying your Oracle Webcenter Portal Framework Application into your JDeveloper’s Integrated Managed Server is so helpful when you were in the development stage, the deployment of your Application into pre-configured Managed Server WC_Spaces like we did in the Oracle Webcenter Portal installation at the introduction tutorial, isn’t recommended approach by Oracle itself as such this new approach will be suggested to be used in case you’re going to deploy your Portal Application into Staging environment.
Oracle Webcenter Portal Framework Application’s Index Page
Before getting started clarifying what’s the home page and how it can be changed, let me introduce you the unknown soldier index.html that’s playing major role in home page determination once Portal Application URL gets accessed.
Index.html is a pure HTML page that’s located under your Portal Application’s web content folder. To find out this resource easily – by JDeveloper or by your actual folder structure, you may open your JDeveloper and point your Portal Project and make sure Group By Directory option is selected from Navigator Display Options. This would help you seeing index.html as it’s in the actual folder upon your file system.
And you will be able after that from seeing index.html beneath Web Content / Public HTML resources.
And if you get navigated into your JDeveloper user’s home folder which is actually the home of your work you will definitely see this resource just like below:
Be careful from expecting that your Portal Applications are having the same file path like i have. This is actually can be controlled and modified, so i recommend you searching about your mywork into your default profile folder beneath folder named jdeveloper.
If you were opened index.html, you may be wondering that it’s not contained a lot of codes, all what it has is just a two major meta statements.
index.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "https://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></meta>
<meta http-equiv="refresh" content="0;url=./faces/wcnav_defaultSelection" />
<title>Portal Home</title>
</head>
<body></body>
</html>
And herein the technical specification that mainly helps you understanding what you did see right now:
- Metadata HTML Tags are used to provide meta information about the HTML document. As most of us know, they’re not displayed on the page but they were machine parse targets.
- You may notice that index.html is having two Metadata Tags; Content-Type and refresh. The content type is so important if your page goes to support another type of encoding or/and content. While refresh is used in conjunction with specified time and URL for achieving redirect mechanism if any.
- Once index.html is rendered and browser has parsed these meta data information, the page would be refreshed instantly – due to 0 time interval, and takes the control away into that resource mentioned in the content’s URL parameter.
- Content’s URL is specified to refer default Portal Navigation Model ./faces/wcnav_defaultSelection.
- Default navigation model has referenced the Pretty URL element pages_home as the Page Hierarchy is the first element therein. Pages is the id of the page hierarchy Portal element that’s defined in the default navigation model and home is the id of the home page that’s defined in the Page Hierarchy element.
And home page defined like below in the pages.xml which is opened in the editor below
If you were replaced ./faces/wcnav_defaultSelection with ./faces/pages_home you will get the same result. As pages and home will refer page hierarchy component and home page defined therein respectively.
Now, let’s see how can these configurations work willingly, either by using the default index redirect or by accessing the pages_home directly.
- Open your JDeveloper on that created Oracle Webcenter Portal Framework Application which includes two Projects, JournalDevPortal & PortalWebAssests.
- Execute your JournalDevPortal project by choosing Run from its menu context after right clicking.
Take into your consideration that once your Integrated Managed Server went down, your JournalDevPortal application will be removed directly. If you want to get this deployment permanently, you should deploy it through using of deployment profile (either using ear or war). As that, by starting up the Integrated Managed Server, your deployment will be right there and ready to serve.
- Type into your browser the following https://10.10.90.3/JournalDevPortal/faces/pages_home and see the result. It should be like below:
You may be wondering from being the pages_home is prefixed with faces. As you may remember that Oracle Webcenter Portal Framework Application is an ADF application with Portal-features, so be sure that all pages can be accessed through JSF manner and that what you’re going to see when it comes to deal with the navigation.
- Modify the order of the pages inside your pages.xml (Through typical editor) will certainly affect the default opened page. See below how we do this re-order by dragging the home to be after about.
- Run your application and make sure you’re already logged in, remember that About page is protected by using the Page Hierarchy Security panel that’s seeing underneath.
- Once you’re logged in you’ll be certainly navigating into home page and that’s so normal as the login action has activated this – Which will be changed latterly.
- Try to type https://10.10.90.3/JournalDevPortal/faces/wcnav_defaultSelection after log in and you should definitely see the below result.
Modifying Index Page
You may noticed that the index.html is displayed firstly and it makes a redirect into next view accordingly. This is so clear when the title of the page becomes Portal Home which is the title of index.html before showing page’s real title like Home or About.
But you may be asking about from where index.html page is specified to be displayed firstly, the good answer will be loudly from web.xml file. Take a look inside you would see the welcome-file-list Tag listed therein:
web.xml
<welcome-file-list>
<welcome-file>/index.html</welcome-file>
</welcome-file-list>
And that value can be ultimately modified by two options:
- Modify the attribute manually.
- Modify the default index page by using Edit Run Configuration “Default” Dialog Box. This dialog can be accessed by selecting Run/Debug/Profile Tab from the shown dialog that’s resulted in from selecting JournalDevPortal’s project properties.
- Click edit on Run Configuration’s default setting to edit launch settings accordingly.
- You may change this by editing the value of the Default Run Target. For this we’ve created a JournalDev.html page and its content is shown here below:
JournalDev.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "https://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"></meta>
<meta http-equiv="refresh" content="0;url=./faces/pages_help" />
<title>JournalDev Portal</title>
</head>
<body></body>
</html>
- Select the new page by browsing it.
- Run the application and see the modifications happened.
- JournalDev HTML page has redirected the control away from it into ./faces/pages_help which will be translated as a normal Portal page using the same concept that we explained.
Portal Pages & Folder Contents Concept
According for importance of page hierarchy component as it’s mainly the major input for the navigation model, it’s so important for you to know that navigation model treat your defined pages and their sub pages as a folder.
To leverage the concept, open your default navigation model and notice the Insert Folder Contents check box drawn beneath the Page Hierarchy element.
So, what’s the Folder concept behind your pages ? to answer this questions, let’s try to enable this and disable it once again and see the difference on the JournalDev Portal Framework Application.
If you get this option disabled, you’ll truly get the following below result:
And if you clicked on the Page Hierarchy gray element, you should see your pages – elements of first level on the hierarchy – populated there.
And if you returned back into enabling this option you would see the all pages and their sub pages displayed in a structural manner down in the hierarchy.
In that, and once Insert Folder Contents option is enabled the Portal Framework will treat your pages as a Folders and so will populate their sub pages as a sub elements while displaying the navigation model.
Modify Login/Logout Landing Page
As you may notice above and through using of Pretty URL, you have the ability to navigate between your pages as though you’re working with normal JSF/ADF application.
Open your faces-config.xml file that’s located under your WEB-INF and look at the navigation cases listed therein:
faces-config.xml
<?xml version="1.0" encoding="windows-1252"?>
<faces-config version="1.2" xmlns="https://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
<view-handler>oracle.webcenter.portalframework.sitestructure.handler.CustomViewHandler</view-handler>
</application>
<lifecycle>
<phase-listener>oracle.webcenter.skin.view.SkinPhaseListener</phase-listener>
</lifecycle>
<managed-bean>
<managed-bean-name>preferenceBean</managed-bean-name>
<managed-bean-class>oracle.webcenter.portalframework.sitestructure.preference.PortalPreferences</managed-bean-class>
<managed-bean-scope>application</managed-bean-scope>
</managed-bean>
<navigation-rule>
<from-view-id>*</from-view-id>
<navigation-case>
<from-outcome>login_success</from-outcome>
<to-view-id>/pages_home</to-view-id>
<redirect/>
</navigation-case>
<navigation-case>
<from-outcome>logout_success</from-outcome>
<to-view-id>/pages_home</to-view-id>
<redirect/>
</navigation-case>
</navigation-rule>
</faces-config>
Herein below the explanation for the faces-config.xml file:
- This faces configuration file will be read by JSF/ADF implementation to populate JSF/ADF framework with the required artifacts.
- One JSF/ADF bean will be created and referenced afterwards.
- Two navigational cases are listed there; one for login success and the second for logout success.
- To control to which the pages the Portal Framework will lead for in case the login_success and logout_success are happened, modify the Pretty URL for the case you want to change.
- By replacing the login_success to view id into pages_about or any Pretty URL you want, you will truly navigate into About page once you’re logged in successfully and the same issue for logout.
Extending Your Domain – Creating WC_CustomPortal Managed Server
According for Oracle documentation, it’s not recommended to deploy your application into pre-configured Oracle Webcenter Portal that’s already created during Oracle Webcenter Portal Installation.
As such, from now on no need for using WC_Spaces nor for any of those ready-made Managed Servers as we already had an Integrated Managed Server for development and now we have a Custom Portal Managed Server for staging purposes.
To prepare your Oracle Custom Portal Managed Server follow instructions below:
- Prepare your CUSTOMDEV_MDS, CUSTOMDEV_WEBCENTER & CUSTOMDEV_ACTIVITIES data sources. A one datasource will be actually used and it’s the CUSTOMDEV_MDS which will be populated with the all meta data that’s defined by the Portal application itself. More upon that will be in the next coming Tutorials.
- Extend your domain by navigating into your Oracle Webcenter Home that’s located in the Middleware home and from bin folder execute config.cmd.
To extend your domain, you may navigate into D:OracleWebCenterOracleWCWL6MiddlewareOracle_WCcommonbin and execute the config.cmd.
- Select your domain that you would extend it.
- Click next and choose Extend my domain using an existing extension template. By browsing Oracle Webcenter directory / common / templates you will find Oracle Portal template required.
- Select Oracle Webcenter Portal Template oracle.wc_custom_portal_template_11.1.1.jar.
- Click Okay and next after that and configure your newly custom domain just like you did with your Managed Servers in the introduction. Take into your consideration the database settings.
- You may configure your three datasources by selecting each one alone and configure it like below and deselected it after then.
- Click next and make sure you’re getting successful database Tests and configure your Custom Portal Managed Server to be one of those managed servers that your node manager aware of. This configuration can be done by dragging your WC_CustomPortal to be under created machine. The same thing is already happened in the introduction.
- Once your extension gets finished, you are now ready for getting it up and connecting your JDeveloper with it.
- Navigate into your node managed home and starting up your node manager that will listen on Port 5556.
Node Manager will allow you managing your servers from one point and either by using AdminServer or Oracle Webcenter Portal Enterprise Manager. From WLS home you may start your managed server. For me, it’s located on D:OracleWebCenterOracleWCWL6Middlewarewlserver_10.3serverbin
- Start your AdminServer by executing startWeblogic.cmd.
- For first time, it’s so better getting your WC_CustomPortal Managed Server up and running by executing startManagedServer.cmd WC_CustomPortal https://10.10.90.3:7001. This will eliminate the need for setting username and password manually as the console will prompt you entering them.
Both of startWeblogic.cmd & StartManagedServer.cmd be actually located under the following path D:OracleWebCenterOracleWCWL6Middlewareuser_projectsdomainsJournalDevbin
- Once your server is up and ready to serve, a notification will be sent for the AdminServer to know that this Server is now up. This process may got failed for several reasons, as we’ve mentioned this in our introduction, the time is now for giving it more slight clarification.
AdminServer notification has been done through JMX and that should connect to the AdminServer for doing that. This connection may use the IPV6 which may lead for destination unreachable and so an exception like Unable to establish JMX Connectivity weblogic.management.mbeanservers.domainruntime will be thrown, preventing you from getting AdminServer notified and that will make both of AdminServer and Enterprise Manager unaware that this server is up. If you tried to deploy your Portal application into your WC_CustomPortal, it’s likely to be failed due to this notification issue. Fixing this issue needs your attention, as you should enforce your Managed Servers to get up and send their notification through using of IPv4. See Appendix A for both of startManagedServe
r.cmd and setDomainEnv.cmd which are modified to enforce IPv4.
- If you’re prompted to enter username and password, enter weblogic/weblogic123. Waiting a while until your WC_CustomPortal become up and running.
- Once your WC_CustomPortal become up and running, your AdminServer and for sure enterprise manager will be aware of that.
- Now, you’re having a ready WC_CustomPortal Managed Server that’s supplied with all required libraries for your Portal Application.
More about WC_CustomPortal will be in the next coming tutorials.
Deploying Your Portal Framework Application Into WC_CustomPortal Managed Server
To get your Portal Application deployed, make sure first of all you have had an established connection. To create a connection to that server, just follow below steps:
- Make sure your WC_CustomPortal Managed Server is up and running.
- From Application Server Navigator, and upon Application Servers node, create new Application Server.
- Choose Integrated Server option and click next.
- Enter the name of the server and select Let JDeveloper manage the lifecycle for this Server Instance.
- Select your domain and you server instance.
- Click next and filling in username and password requested and click next.
- Filling in required hostname and domain and left others as is.
- Click next and make sure your connection Test is finished successfully.
This Test actually will communicate with AdminServer to specify whether the connected server is up or not. So be careful to make sure you’re getting AdminServer up and running.
- Click next and finish.
- From your Portal Application Project, right-click, select deploy and the default option located there. This default option can be overridden if you want by creating non-default deployment profile. This is actually coming in the next coming tutorials.
- Click next and choose deploy to Application Server.
- Click next and choose your newly created server.
- Click next and select Deploy to selected instances in the domain. And select WC_CustomPortal server.
- Click next and finish.
- Waiting a while till the deployment takes the place.
- If you’re prompted to select the Metadata repository select that one is relevant for the custom and type the Partition Name. If you were not deployed your Application previously, this partition name will be created, otherwise, the values will be overridden.
Metadata Repository is so important concept that we’re going to explain. But you may consider it for now as a location (May be XML or database based) that’s used to define your Portal Framework Application Artifacts. Its values will be populated with MAR file which is created while deploying and it is stand for Metadata Archive File.
- Click deploy. Waiting a while before console has figured out your deployment URL that you may use to access your Portal Application.
This deployment is done on WAR level, in the next coming Tutorials, you will learn the EAR level deployment that may or may not contain the static PortalWebAssests second project.
- If you were deployed your Application Successfully you should see the below screen as well as ability to access your Application through using of URL figured out bottom there.
- Typing https://10.10.90.3:8892/JournalDevPortal into your browser will make index.html selected automatically and by that the default selection navigation model will be chosen.
Summary
Oracle Webcenter provides facilities to modify the way in which the home page is specified. In addition for that you may also modify the page that the Portal will lead you for after success login or/and success logout. This tutorial is intended to provide you all of needed information to understand the way in which Portal Application has configured this.
Also, it’s time now to prepare our staging environment and that’s happily can be done thorugh extending our domain by adding newly Custom Portal Managed server that’s already contained all of these required libraries to get Portal Application deployed successfully and ready to use.
Appendix A
This Appendix is cr
eated to help the developer by pass the connection exception that may result in when the Managed Server uses IPv6 to notify the AdminServer about its status. you may find below startDomainEnv.cmd and startManagedWeblogic.cmd updates happened upon JAVA_OPTIONS, so you may use them or edit your command files to be identical.
setDomainEnv.cmd
@ECHO OFF
@REM WARNING: This file is created by the Configuration Wizard.
@REM Any changes to this script may be lost when adding extensions to this configuration.
@REM *************************************************************************
@REM This script is used to setup the needed environment to be able to start Weblogic Server in this domain.
@REM
@REM This script initializes the following variables before calling commEnv to set other variables:
@REM
@REM WL_HOME - The BEA home directory of your WebLogic installation.
@REM JAVA_VM - The desired Java VM to use. You can set this environment variable before calling
@REM this script to switch between Sun or BEA or just have the default be set.
@REM JAVA_HOME - Location of the version of Java used to start WebLogic
@REM Server. Depends directly on which JAVA_VM value is set by default or by the environment.
@REM USER_MEM_ARGS - The variable to override the standard memory arguments
@REM passed to java.
@REM PRODUCTION_MODE - The variable that determines whether Weblogic Server is started in production mode.
@REM DOMAIN_PRODUCTION_MODE
@REM - The variable that determines whether the workshop related settings like the debugger,
@REM testconsole or iterativedev should be enabled. ONLY settable using the
@REM command-line parameter named production
@REM NOTE: Specifying the production command-line param will force
@REM the server to start in production mode.
@REM
@REM Other variables used in this script include:
@REM SERVER_NAME - Name of the weblogic server.
@REM JAVA_OPTIONS - Java command-line options for running the server. (These
@REM will be tagged on to the end of the JAVA_VM and
@REM MEM_ARGS)
@REM
@REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
@REM (https://download.oracle.com/docs/cd/E23943_01/web.1111/e13708/overview.htm).
@REM *************************************************************************
set COMMON_COMPONENTS_HOME=D:OracleWebCenterOracleWCWL6Middlewareoracle_common
for %%i in ("%COMMON_COMPONENTS_HOME%") do set COMMON_COMPONENTS_HOME=%%~fsi
set UCM_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_ECM
for %%i in ("%UCM_ORACLE_HOME%") do set UCM_ORACLE_HOME=%%~fsi
set IRM_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_ECM
set WC_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_WC
set APPLICATIONS_DIRECTORY=D:OracleWebCenterOracleWCWL6Middlewareuser_projectsapplicationsJournalDev
set WC_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_WC
set WCPS_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_WC
set PORTLET_ORACLE_HOME=D:OracleWebCenterOracleWCWL6Middlewareoracle_common
set WC_ORACLE_HOME=D:OracleWebCenterOracleWCWL6MiddlewareOracle_WC
set WL_HOME=D:OracleWebCenterOracleWCWL6Middlewarewlserver_10.3
for %%i in ("%WL_HOME%") do set WL_HOME=%%~fsi
set BEA_JAVA_HOME=D:OracleWebCenterOracleWCWL6Middlewarejrockit_160_29_D1.2.0-10
set SUN_JAVA_HOME=D:OracleWebCenterOracleWCWL6Middlewarejdk160_29
if "%JAVA_VENDOR%"=="Oracle" (
set JAVA_HOME=%BEA_JAVA_HOME%
) else (
if "%JAVA_VENDOR%"=="Sun" (
set JAVA_HOME=%SUN_JAVA_HOME%
) else (
set JAVA_VENDOR=Sun
set JAVA_HOME=D:OracleWebCenterOracleWCWL6Middlewarejdk160_29
)
)
@REM We need to reset the value of JAVA_HOME to get it shortened AND
@REM we can not shorten it above because immediate variable expansion will blank it
set JAVA_HOME=%JAVA_HOME%
for %%i in ("%JAVA_HOME%") do set JAVA_HOME=%%~fsi
set SAMPLES_HOME=%WL_HOME%samples
set DOMAIN_HOME=D:OracleWebCenterOracleWCWL6Middlewareuser_projectsdomainsJournalDev
for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
set LONG_DOMAIN_HOME=D:OracleWebCenterOracleWCWL6Middlewareuser_projectsdomainsJournalDev
if "%DEBUG_PORT%"=="" (
set DEBUG_PORT=8453
)
if "%SERVER_NAME%"=="" (
set SERVER_NAME=AdminServer
)
set DERBY_FLAG=false
set enableHotswapFlag=
set PRODUCTION_MODE=
set doExitFlag=false
set verboseLoggingFlag=false
for %%p in (%*) do call :SET_PARAM %%p
GOTO :CMD_LINE_DONE
:SET_PARAM
for %%q in (%1) do set noQuotesParam=%%~q
if /i "%noQuotesParam%" == "nodebug" (
set debugFlag=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "production" (
set DOMAIN_PRODUCTION_MODE=true
GOTO :EOF
)
if /i "%noQuotesParam%" == "notestconsole" (
set testConsoleFlag=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "noiterativedev" (
set iterativeDevFlag=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "noLogErrorsToConsole" (
set logErrorsToConsoleFlag=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "noderby" (
set DERBY_FLAG=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "doExit" (
set doExitFlag=true
GOTO :EOF
)
if /i "%noQuotesParam%" == "noExit" (
set doExitFlag=false
GOTO :EOF
)
if /i "%noQuotesParam%" == "verbose" (
set verboseLoggingFlag=true
GOTO :EOF
)
if /i "%noQuotesParam%" == "enableHotswap" (
set enableHotswapFlag=-javaagent:%WL_HOME%serverlibdiagnostics-agent.jar
GOTO :EOF
) else (
set PROXY_SETTINGS=%PROXY_SETTINGS% %1
)
GOTO :EOF
:CMD_LINE_DONE
set MEM_DEV_ARGS=
if "%DOMAIN_PRODUCTION_MODE%"=="true" (
set PRODUCTION_MODE=%DOMAIN_PRODUCTION_MODE%
)
if "%PRODUCTION_MODE%"=="true" (
set debugFlag=false
set testConsoleFlag=false
set iterativeDevFlag=false
set logErrorsToConsoleFlag=false
)
@REM If you want to override the default Patch Classpath, Library Path and Path for this domain,
@REM Please uncomment the following lines and add a valid value for the environment variables
@REM set PATCH_CLASSPATH=[myPatchClasspath] (windows)
@REM set PATCH_LIBPATH=[myPatchLibpath] (windows)
@REM set PATCH_PATH=[myPatchPath] (windows)
@REM PATCH_CLASSPATH=[myPatchClasspath] (unix)
@REM PATCH_LIBPATH=[myPatchLibpath] (unix)
@REM PATCH_PATH=[myPatchPath] (unix)
call "%WL_HOME%commonbincommEnv.cmd"
set WLS_HOME=%WL_HOME%server
set XMS_SUN_64BIT=256
set XMS_SUN_32BIT=256
set XMX_SUN_64BIT=512
set XMX_SUN_32BIT=512
set XMS_JROCKIT_64BIT=256
set XMS_JROCKIT_32BIT=256
set XMX_JROCKIT_64BIT=512
set XMX_JROCKIT_32BIT=512
set XMS_SUN_64BIT=512
set XMS_SUN_32BIT=512
set XMX_SUN_64BIT=1024
set XMX_SUN_32BIT=1024
set XMS_JROCKIT_64BIT=512
set XMS_JROCKIT_32BIT=512
set XMX_JROCKIT_64BIT=1024
set XMX_JROCKIT_32BIT=1024
set XMS_SUN_64BIT=512
set XMS_SUN_32BIT=512
set XMX_SUN_64BIT=1024
set XMX_SUN_32BIT=1024
set XMS_JROCKIT_64BIT=512
set XMS_JROCKIT_32BIT=512
set XMX_JROCKIT_64BIT=1024
set XMX_JROCKIT_32BIT=1024
if "%JAVA_VENDOR%"=="Sun" (
set WLS_MEM_ARGS_64BIT=-Xms256m -Xmx512m
set WLS_MEM_ARGS_32BIT=-Xms256m -Xmx512m
) else (
set WLS_MEM_ARGS_64BIT=-Xms512m -Xmx512m
set WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
)
if "%JAVA_VENDOR%"=="Oracle" (
set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_JROCKIT_64BIT%m -Xmx%XMX_JROCKIT_64BIT%m
set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_JROCKIT_32BIT%m -Xmx%XMX_JROCKIT_32BIT%m
) else (
set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_SUN_64BIT%m -Xmx%XMX_SUN_64BIT%m
set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_SUN_32BIT%m -Xmx%XMX_SUN_32BIT%m
)
set MEM_ARGS_64BIT=%CUSTOM_MEM_ARGS_64BIT%
set MEM_ARGS_32BIT=%CUSTOM_MEM_ARGS_32BIT%
if "%JAVA_USE_64BIT%"=="true" (
set MEM_ARGS=%MEM_ARGS_64BIT%
) else (
set MEM_ARGS=%MEM_ARGS_32BIT%
)
set MEM_PERM_SIZE_64BIT=-XX:PermSize=128m
set MEM_PERM_SIZE_32BIT=-XX:PermSize=128m
if "%JAVA_USE_64BIT%"=="true" (
set MEM_PERM_SIZE=%MEM_PERM_SIZE_64BIT%
) else (
set MEM_PERM_SIZE=%MEM_PERM_SIZE_32BIT%
)
set MEM_MAX_PERM_SIZE_64BIT=-XX:MaxPermSize=512m
set MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=512m
if "%JAVA_USE_64BIT%"=="true" (
set MEM_MAX_PERM_SIZE=%MEM_MAX_PERM_SIZE_64BIT%
) else (
set MEM_MAX_PERM_SIZE=%MEM_MAX_PERM_SIZE_32BIT%
)
if "%JAVA_VENDOR%"=="Sun" (
if "%PRODUCTION_MODE%"=="" (
set MEM_DEV_ARGS=-XX:CompileThreshold=8000 %MEM_PERM_SIZE%
)
)
@REM Had to have a separate test here BECAUSE of immediate variable expansion on windows
if "%JAVA_VENDOR%"=="Sun" (
set MEM_ARGS=%MEM_ARGS% %MEM_DEV_ARGS% %MEM_MAX_PERM_SIZE%
)
if "%JAVA_VENDOR%"=="HP" (
set MEM_ARGS=%MEM_ARGS% %MEM_MAX_PERM_SIZE%
)
if "%JAVA_VENDOR%"=="Apple" (
set MEM_ARGS=%MEM_ARGS% %MEM_MAX_PERM_SIZE%
)
@REM IF USER_MEM_ARGS the environment variable is set, use it to override ALL MEM_ARGS values
if NOT "%USER_MEM_ARGS%"=="" (
set MEM_ARGS=%USER_MEM_ARGS%
)
set ORACLE_DOMAIN_CONFIG_DIR=%DOMAIN_HOME%configfmwconfig
for %%i in ("%ORACLE_DOMAIN_CONFIG_DIR%") do set ORACLE_DOMAIN_CONFIG_DIR=%%~fsi
set WLS_JDBC_REMOTE_ENABLED=-Dweblogic.jdbc.remoteEnabled=false
if "%WC_OHOME_ARGUMENT%"=="" (
set WC_OHOME_ARGUMENT=-Dwc.oracle.home=%WC_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dwc.oracle.home=%WC_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
)
if "%WC_OHOME_ARGUMENT%"=="" (
set WC_OHOME_ARGUMENT=-Dwc.oracle.home=%WC_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dwc.oracle.home=%WC_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
)
if "%PORTLET_OHOME_ARGUMENT%"=="" (
set PORTLET_OHOME_ARGUMENT=-Dportlet.oracle.home=%PORTLET_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dportlet.oracle.home=%PORTLET_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
)
if "%WC_OHOME_ARGUMENT%"=="" (
set WC_OHOME_ARGUMENT=-Dwc.oracle.home=%WC_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Dwc.oracle.home=%WC_ORACLE_HOME% %EXTRA_JAVA_PROPERTIES%
)
set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME%
set ALT_TYPES_DIR=%COMMON_COMPONENTS_HOME%modulesoracle.ossoiap_11.1.1,%COMMON_COMPONENTS_HOME%modulesoracle.oamprovider_11.1.1,%COMMON_COMPONENTS_HOME%modulesoracle.jps_11.1.1
set PROTOCOL_HANDLERS=oracle.mds.net.protocol
if "%JAVA_VENDOR%"=="Sun" (
set EXTRA_JAVA_PROPERTIES=-XX:+UseParallelGC -XX:+DisableExplicitGC %EXTRA_JAVA_PROPERTIES%
) else (
if "%JAVA_VENDOR%"=="Oracle" (
set EXTRA_JAVA_PROPERTIES=-Djrockit.codegen.newlockmatching=true %EXTRA_JAVA_PROPERTIES%
) else (
set EXTRA_JAVA_PROPERTIES=-XX:+UseParallelGC -XX:+DisableExplicitGC %EXTRA_JAVA_PROPERTIES%
)
)
set PROTOCOL_HANDLERS=%PROTOCOL_HANDLERS:;="|"%
@REM To use Java Authorization Contract for Containers (JACC) in this domain,
@REM please uncomment the following section. If there are multiple machines in
@REM your domain, be sure to edit the setDomainEnv in the associated domain on
@REM each machine.
@REM
@REM -Djava.security.manager
@REM -Djava.security.policy=location of weblogic.policy
@REM -Djavax.security.jacc.policy.provider=weblogic.security.jacc.simpleprovider.SimpleJACCPolicy
@REM -Djavax.security.jacc.PolicyConfigurationFactory.provider=weblogic.security.jacc.simpleprovider.PolicyConfigurationFactoryImpl
@REM -Dweblogic.security.jacc.RoleMapperFactory.provider=weblogic.security.jacc.simpleprovider.RoleMapperFactoryImpl
if "%JAVA_VENDOR%"=="Oracle" (
set EXTRA_JAVA_PROPERTIES=-XX:+UseLargePagesForHeap %EXTRA_JAVA_PROPERTIES%
)
set EXTRA_JAVA_PROPERTIES=-Doracle.webcenter.tagging.scopeTags=false %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=-Djava.awt.headless=true %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dipm.oracle.home=D:OracleWebCenterOracleWCWL6MiddlewareOracle_ECM
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Doracle.capture.home=D:OracleWebCenterOracleWCWL6MiddlewareOracle_ECM
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Ducm.oracle.home=%UCM_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dirm.oracle.home=%IRM_ORACLE_HOME%
set EXTRA_JAVA_PROPERTIES=-Doracle.webcenter.tagging.scopeTags=false %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=-Doracle.webcenter.analytics.disable-native-partitioning=false %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=-DUSE_JAAS=false -Djps.policystore.hybrid.mode=false -Djps.combiner.optimize.lazyeval=true -Djps.combiner.optimize=true -Djps.auth=ACC -Doracle.core.ojdl.logging.usercontextprovider=oracle.core.ojdl.logging.impl.UserContextImpl %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=D:OracleWebCenterOracleWCWL6Middlewareoracle_common -Djava.awt.headless=true
set EXTRA_JAVA_PROPERTIES=-Dtangosol.coherence.log=jdk -DjiveHome=%DOMAIN_HOME%configfmwconfigservers%SERVER_NAME%owc_discussions %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=-Djps.auth.debug=false %EXTRA_JAVA_PROPERTIES%
set EXTRA_JAVA_PROPERTIES=-Dcommon.components.home=%COMMON_COMPONENTS_HOME% -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=%DOMAIN_HOME% -Djrockit.optfile=%COMMON_COMPONENTS_HOME%modulesoracle.jrf_11.1.1jrocket_optfile.txt -Doracle.server.config.dir=%ORACLE_DOMAIN_CONFIG_DIR%servers%SERVER_NAME% -Doracle.domain.config.dir=%ORACLE_DOMAIN_CONFIG_DIR% -Digf.arisidbeans.carmlloc=%ORACLE_DOMAIN_CONFIG_DIR%carml -Digf.arisidstack.home=%ORACLE_DOMAIN_CONFIG_DIR%arisidprovider -Doracle.security.jps.config=%DOMAIN_HOME%configfmwconfigjps-config.xml -Doracle.deployed.app.dir=%DOMAIN_HOME%servers%SERVER_NAME%tmp_WL_user -Doracle.deployed.app.ext=- -Dweblogic.alternateTypesDirectory=%ALT_TYPES_DIR% -Djava.protocol.handler.pkgs=%PROTOCOL_HANDLERS% %WLS_JDBC_REMOTE_ENABLED% %EXTRA_JAVA_PROPERTIES%
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %EXTRA_JAVA_PROPERTIES%
set ARDIR=%WL_HOME%serverlib
pushd %LONG_DOMAIN_HOME%
@REM Clustering support (edit for your cluster!)
if "%ADMIN_URL%"=="" (
@REM The then part of this block is telling us we are either starting an admin server OR we are non-clustered
set CLUSTER_PROPERTIES=-Dweblogic.management.discover=true
) else (
set CLUSTER_PROPERTIES=-Dweblogic.management.discover=false -Dweblogic.management.server=%ADMIN_URL%
)
if NOT "%LOG4J_CONFIG_FILE%"=="" (
set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Dlog4j.configuration=file:%LOG4J_CONFIG_FILE%
)
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %CLUSTER_PROPERTIES%
set JAVA_DEBUG=
if "%debugFlag%"=="true" (
set JAVA_DEBUG=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=%DEBUG_PORT%,server=y,suspend=n -Djava.compiler=NONE
set JAVA_OPTIONS=%JAVA_OPTIONS% %enableHotswapFlag% -Djava.net.preferIPv4Stack=true -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole...
) else (
set JAVA_OPTIONS=%JAVA_OPTIONS% %enableHotswapFlag% -da -Djava.net.preferIPv4Stack=true
)
if NOT exist %JAVA_HOME%lib (
echo The JRE was not found in directory %JAVA_HOME%. ^(JAVA_HOME^)
echo Please edit your environment and set the JAVA_HOME
echo variable to point to the root directory of your Java installation.
popd
pause
GOTO :EOF
)
if "%DERBY_FLAG%"=="true" (
set DATABASE_CLASSPATH=%DERBY_CLASSPATH%
) else (
set DATABASE_CLASSPATH=%DERBY_CLIENT_CLASSPATH%
)
if NOT "%POST_CLASSPATH%"=="" (
set POST_CLASSPATH=%COMMON_COMPONENTS_HOME%modulesoracle.jrf_11.1.1jrf.jar;%POST_CLASSPATH%
) else (
set POST_CLASSPATH=%COMMON_COMPONENTS_HOME%modulesoracle.jrf_11.1.1jrf.jar
)
if NOT "%PRE_CLASSPATH%"=="" (
set PRE_CLASSPATH=%COMMON_COMPONENTS_HOME%modulesoracle.jdbc_11.1.1ojdbc6dms.jar;%PRE_CLASSPATH%
) else (
set PRE_CLASSPATH=%COMMON_COMPONENTS_HOME%modulesoracle.jdbc_11.1.1ojdbc6dms.jar
)
if "%PORTLET_ORACLE_HOME%"=="" (
set POST_CLASSPATH=%WC_ORACLE_HOME%webcentermodulesoracle.portlet.server_11.1.1oracle-portlet-api.jar;%POST_CLASSPATH%
)
set POST_CLASSPATH=%WCPS_ORACLE_HOME%wcps-services-appmodulesoracle.wcps_11.1.1wcps-connection-mbeans.jar;%POST_CLASSPATH%
set POST_CLASSPATH=%PORTLET_ORACLE_HOME%webcentermodulesoracle.portlet.server_11.1.1oracle-portlet-api.jar;%POST_CLASSPATH%
set POST_CLASSPATH=%COMMON_COMPONENTS_HOME%soamodulescommons-cli-1.1.jar;%COMMON_COMPONENTS_HOME%soamodulesoracle.soa.mgmt_11.1.1soa-infra-mgmt.jar;%POST_CLASSPATH%
if NOT "%DATABASE_CLASSPATH%"=="" (
if NOT "%POST_CLASSPATH%"=="" (
set POST_CLASSPATH=%POST_CLASSPATH%;%DATABASE_CLASSPATH%
) else (
set POST_CLASSPATH=%DATABASE_CLASSPATH%
)
)
if NOT "%ARDIR%"=="" (
if NOT "%POST_CLASSPATH%"=="" (
set POST_CLASSPATH=%POST_CLASSPATH%;%ARDIR%xqrl.jar
) else (
set POST_CLASSPATH=%ARDIR%xqrl.jar
)
)
@REM PROFILING SUPPORT
set JAVA_PROFILE=
set SERVER_CLASS=weblogic.Server
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%
set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -Djava.net.preferIPv4Stack=true -Dwlw.iterativeDev=%iterativeDevFlag% -Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag%
if "%PRODUCTION_MODE%"=="true" (
set JAVA_OPTIONS= -Djava.net.preferIPv4Stack=true -Dweblogic.ProductionModeEnabled=true %JAVA_OPTIONS%
)
@REM -- Setup properties so that we can save stdout and stderr to files
if NOT "%WLS_STDOUT_LOG%"=="" (
echo Logging WLS stdout to %WLS_STDOUT_LOG%
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.net.preferIPv4Stack=true -Dweblogic.Stdout=%WLS_STDOUT_LOG%
)
if NOT "%WLS_STDERR_LOG%"=="" (
echo Logging WLS stderr to %WLS_STDERR_LOG%
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.net.preferIPv4Stack=true -Dweblogic.Stderr=%WLS_STDERR_LOG%
)
@REM ADD EXTENSIONS TO CLASSPATHS
if NOT "%EXT_PRE_CLASSPATH%"=="" (
if NOT "%PRE_CLASSPATH%"=="" (
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%
) else (
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%
)
)
set POST_CLASSPATH=%POST_CLASSPATH%;%UCM_ORACLE_HOME%ucmidcjlibidcloader.jar;%UCM_ORACLE_HOME%ucmidccomponentsNativeOsUtilsclasses-NativeOsUtils.jar
call "%UCM_ORACLE_HOME%ucmidcbinidcCommEnv.cmd"
if NOT "%EXT_POST_CLASSPATH%"=="" (
if NOT "%POST_CLASSPATH%"=="" (
set POST_CLASSPATH=%POST_CLASSPATH%;%EXT_POST_CLASSPATH%
) else (
set POST_CLASSPATH=%EXT_POST_CLASSPATH%
)
)
if NOT "%WEBLOGIC_EXTENSION_DIRS%"=="" (
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.net.preferIPv4Stack=true -Dweblogic.ext.dirs=%WEBLOGIC_EXTENSION_DIRS%
)
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.net.preferIPv4Stack=true
@REM SET THE CLASSPATH
if NOT "%WLP_POST_CLASSPATH%"=="" (
if NOT "%CLASSPATH%"=="" (
set CLASSPATH=%WLP_POST_CLASSPATH%;%CLASSPATH%
) else (
set CLASSPATH=%WLP_POST_CLASSPATH%
)
)
if NOT "%POST_CLASSPATH%"=="" (
if NOT "%CLASSPATH%"=="" (
set CLASSPATH=%POST_CLASSPATH%;%CLASSPATH%
) else (
set CLASSPATH=%POST_CLASSPATH%
)
)
if NOT "%WEBLOGIC_CLASSPATH%"=="" (
if NOT "%CLASSPATH%"=="" (
set CLASSPATH=%WEBLOGIC_CLASSPATH%;%CLASSPATH%
) else (
set CLASSPATH=%WEBLOGIC_CLASSPATH%
)
)
if NOT "%PRE_CLASSPATH%"=="" (
set CLASSPATH=%PRE_CLASSPATH%;%CLASSPATH%
)
if NOT "%JAVA_VENDOR%"=="BEA" (
set JAVA_VM=%JAVA_VM% %JAVA_DEBUG% %JAVA_PROFILE%
) else (
set JAVA_VM=%JAVA_VM% %JAVA_DEBUG% %JAVA_PROFILE%
)
startManagedWeblogic.cmd
@ECHO OFF
@REM WARNING: This file is created by the Configuration Wizard.
@REM Any changes to this script may be lost when adding extensions to this configuration.
SETLOCAL
@REM --- Start Functions ---
GOTO :ENDFUNCTIONS
:usage
echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
echo them in command line:
echo Usage: %1 SERVER_NAME {ADMIN_URL}
echo for example:
echo %1 managedserver1 https://mohammad-amr-lt:7001
GOTO :EOF
:ENDFUNCTIONS
@REM --- End Functions ---
@REM *************************************************************************
@REM This script is used to start a managed WebLogic Server for the domain in
@REM the current working directory. This script can either read in the SERVER_NAME and
@REM ADMIN_URL as positional parameters or will read them from environment variables that are
@REM set before calling this script. If SERVER_NAME is not sent as a parameter or exists with a value
@REM as an environment variable the script will EXIT. If the ADMIN_URL value cannot be determined
@REM by reading a parameter or from the environment a default value will be used.
@REM
@REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
@REM (https://download.oracle.com/docs/cd/E23943_01/web.1111/e13708/overview.htm)
@REM *************************************************************************
@REM Set SERVER_NAME to the name of the server you wish to start up.
set DOMAIN_NAME=JournalDev
set ADMIN_URL=https://mohammad-amr-lt:7001
@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=
set WLS_PW=
@REM Set JAVA_OPTIONS to the java flags you want to pass to the vm. i.e.:
@REM set JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value
set JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true -Dweblogic.security.SSL.trustedCAKeyStore="D:OracleWebCenterOracleWCWL6Middlewarewlserver_10.3serverlibcacerts" %JAVA_OPTIONS%
@REM Set JAVA_VM to the java virtual machine you want to run. For instance:
@REM set JAVA_VM=-server
set JAVA_VM=
@REM Set SERVER_NAME and ADMIN_URL, they must by specified before starting
@REM a managed server, detailed information can be found at
@REM https://download.oracle.com/docs/cd/E23943_01/web.1111/e13708/overview.htm
if "%1"=="" (
if "%SERVER_NAME%"=="" (
CALL :usage %0
GOTO :EOF
)
) else (
set SERVER_NAME=%1
shift
)
if "%1"=="" (
if "%ADMIN_URL%"=="" (
CALL :usage %0
GOTO :EOF
)
) else (
set ADMIN_URL=%1
shift
)
@REM Export the admin_url whether the user specified it OR it was sent on the command-line
set ADMIN_URL=%ADMIN_URL%
set SERVER_NAME=%SERVER_NAME%
set DOMAIN_HOME=D:OracleWebCenterOracleWCWL6Middlewareuser_projectsdomainsJournalDev
if "%1"=="" (
@REM Call Weblogic Server with our default params since the user did not specify any other ones
call "%DOMAIN_HOME%binstartWebLogic.cmd" nodebug noderby noiterativedev notestconsole noLogErrorsToConsole
) else (
@REM Call Weblogic Server with the params the user sent in INSTEAD of the defaults
call "%DOMAIN_HOME%binstartWebLogic.cmd" %1 %2 %3 %4 %5 %6 %7 %8 %9
)
ENDLOCAL