Installing WebLogic application as Windows Service

Starting with tool Release 8.98.3 Oracle has supported Windows 2008 64bit platform to host JDEdwards EnterpriseOne web application over WebLogic 10.3.2 version. WebLogic is the core of Oracle Fusion Middleware architecture.

WebLogic typical installation put software on Windows 2008 server as application not as Windows Service. This article want to explain the command to execute to define WebLogic Admin Server, Nome Manager and JDEdwards web application components as Windows services.





How to configure NODE MANAGER

To install WebLogic Node Manager components as Windows service must be executed “installNodeMgrSvc.cmd” command file. This file is located under $WLS_HOME\server\bin\ (where WLS_HOME is directory where WebLogic is installed). On Windows 2008 to execute the command you must open a Windows command prompt as Administrator (using “Run as administrator” ).





How to configure ADMIN SERVER



Must be executeted these steps

1) Create directory “security” under E:\Oracle\Middleware\user_projects\domains\E1_Apps\servers\AdminServer

2) In this directory create a file named “boot.properties” and write in this file two variable user and password specified during WebLogic installation for example

username=weblogic

password=welcome1

When you’ll start Admin server as service these information will be automatically crypted

3) Create a command file and name it for example “installAdmServer_Service.cmd”. It’s not important where you’ll put it. Write these information into the file

SETLOCAL

set DOMAIN_NAME=E1_Apps (Domain created during WebLogic installation)

set USERDOMAIN_HOME=E:\Oracle\Middleware\user_projects\domains\E1_Apps

set SERVER_NAME=AdminServer

set PRODUCTION_MODE=true

cd %USERDOMAIN_HOME%

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

call "E:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"

ENDLOCAL

4) Update file installsvc.cmd located under E:\Oracle\Middleware\wlserver_10.3\server\bin directory adding clause

-log:"E:\Oracle\Middleware\user_projects\domains\E1_Apps\AdminServer-stdout.txt"

To the command "%WL_HOME%\server\bin\beasvc" at the bottom of this file. This clause allow to generate log specifically for AdminServer application.

5) Execute installAdmServer_Service.cmd created at step 3 from a windows command prompt opened always with “Run As Administrator”

6) Compliments!!! You have installed WebLogic Admin server as Windows service!!!!

منقول من
http://www.j4jde.com/jde/34-cnc/98-weblogic-windows-service

لعمل سيرفيس اتوماتيك للفورم سيرفر 11G

For a managed server e.g WLS_FORMS

1. Create a text file

%MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties

Add the following lines

username=weblogic
password=<the weblogic username password e.g manager11g)>

As soon as you start the managed server the username and password values in this file will be encrypted. The alternative approach - like for AdminServer - is to specify WLS_USER and WLS_PW in the wrapper cmd script. See next point

2. Create a command script called installWLSFORMS_Service.cmd which has lines like


SETLOCAL
set DOMAIN_NAME=ClassicDomain
set USERDOMAIN_HOME=C:\middleware\FMW11g\user_projects\domains\ClassicDomain
set SERVER_NAME=WLS_FORMS
set PRODUCTION_MODE=true
set ADMIN_URL=http://mymachine.mycompany.com:7001
cd %USERDOMAIN_HOME%
call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
call "C:\middleware\FMW11g\wlserver_10.3\server\bin\installSvc.cmd"
ENDLOCAL

Notes:

a) The ADMIN_URL value should reference the AdminServer hostname and listen port

The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.

c) Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error

<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server

3. Now run "installWLSFORMS_Service.cmd". The Service should be installed, it will have a name like ""beasvc %DOMAIN_NAME%_%SERVER_NAME%" e.g

beasvc ClassicDomain_WLS_FORMS

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.

And Finally:

The following enhancement request exists regards automating the creation of such services in a future release of Fusion Middleware 11g

لعمل service automatic start up للريبورت سيرفر
يتم عمل نفس الخطوة السابقة مع تعديل WLS_FORMS الى WLS_REPORTS
واضافة BOOT.PROBERTIES الى فولدر SECURTY الخاص بالريبورت
وتعديل الملف installWLSREPORTS_Service.cmd

بالتوفيق ان شاء الله

إخواني واحبتي في الله

اقدم لكم فيديو لكيفية تسطيب اوراكل فورمز 11 جي وكذلك ريبورت سيرفر كاملا من الألف الى الياء

How to install Oracle Developer forms and reports with weblogic configuration + Database + RCU

مهم جدا مراعاة الإصدارات الموجودة والتي تظهر في الفيديو

نسألكم الدعاء لي ولوالدي ولكل المسلمين.

مشكور يا sakr_orcl
بس وين الفيديو

فيديو اية ؟؟ حد جاب سيرة فيديو ؟؟؟


الرابط الأول
طبعا لازم تكون مستطب 2008 server with last update

http://www.mediafire.com/file/76i0b19pdhqgoab/Sakr1.7z

http://www.mediafire.com/file/2ido7j1q413ksy1/Sakr2.7z

http://www.mediafire.com/file/17ntxruu7ncj6rc/Sakr3.7z

http://www.mediafire.com/file/iuz3ebppdt204e2/Sakr4.7z

http://www.mediafire.com/file/2dmovpdrx5tekdy/Sakr5.7z

http://www.mediafire.com/file/c9403un4fgdrrcg/Sakr6.7z

http://www.mediafire.com/file/id9lmodffgg9qk2/Sakr7.7z

http://www.mediafire.com/file/9iqvx12n2ed8vp0/Sakr8.7z

http://www.mediafire.com/file/rlac6714a1dcahf/Sakr9.7z

http://www.mediafire.com/file/yms5p5xzy62h9b5/Sakr10.7z

http://www.mediafire.com/file/yfgmatiqq9969m9/Sakr11.7z

بالتوفيق ان شاء الله

ولسة فية تكملة ان شاء الله

ونسألكم خالص الدعاء

خليل صقر

طبعا محدش يحاول يهزر ويجرب على رامات اقل من 4 جيجا
ومنتسوش تعمل virual memory
من 4000 الى 8000
قبل بدء setup

Invalid or Deleted File.


Please upload it again

 

Installing WebLogic application as Windows Service

 

Starting with tool Release 8.98.3 Oracle has supported Windows 2008 64bit platform to host JDEdwards EnterpriseOne web application over WebLogic 10.3.2 version. WebLogic is the core of Oracle Fusion Middleware architecture.

 

WebLogic typical installation put software on Windows 2008 server as application not as Windows Service. This article want to explain the command to execute to define WebLogic Admin Server, Nome Manager and JDEdwards web application components as Windows services.

 

 

 

 

 

How to configure NODE MANAGER

 

To install WebLogic Node Manager components as Windows service must be executed “installNodeMgrSvc.cmd” command file. This file is located under $WLS_HOME\server\bin\ (where WLS_HOME is directory where WebLogic is installed). On Windows 2008 to execute the command you must open a Windows command prompt as Administrator (using “Run as administrator” ).

 

 

 

 

 

How to configure ADMIN SERVER

 

 

 

Must be executeted these steps

 

1) Create directory “security” under E:\Oracle\Middleware\user_projects\domains\E1_Apps\servers\AdminServer

 

2) In this directory create a file named “boot.properties” and write in this file two variable user and password specified during WebLogic installation for example

 

username=weblogic

 

password=welcome1

 

When you’ll start Admin server as service these information will be automatically crypted

 

3) Create a command file and name it for example “installAdmServer_Service.cmd”. It’s not important where you’ll put it. Write these information into the file

 

SETLOCAL

 

set DOMAIN_NAME=E1_Apps (Domain created during WebLogic installation)

 

set USERDOMAIN_HOME=E:\Oracle\Middleware\user_projects\domains\E1_Apps

 

set SERVER_NAME=AdminServer

 

set PRODUCTION_MODE=true

 

cd %USERDOMAIN_HOME%

 

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

 

call "E:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"

 

ENDLOCAL

 

4) Update file installsvc.cmd located under E:\Oracle\Middleware\wlserver_10.3\server\bin directory adding clause

 

-log:"E:\Oracle\Middleware\user_projects\domains\E1_Apps\AdminServer-stdout.txt"

 

To the command "%WL_HOME%\server\bin\beasvc" at the bottom of this file. This clause allow to generate log specifically for AdminServer application.

 

5) Execute installAdmServer_Service.cmd created at step 3 from a windows command prompt opened always with “Run As Administrator”

 

6) Compliments!!! You have installed WebLogic Admin server as Windows service!!!!

 

منقول من

http://www.j4jde.com/jde/34-cnc/98-weblogic-windows-service

 

شكرا جزيلا أخي على المجهود الرائع لكن لم أستطع تشغيل الفورم رغم أنني اتبعت خطواتك حرفيا

لا أدري أين المشكلة

أتمنى مزيدا من الشرح و شكرا

 

 

Installing WebLogic application as Windows Service

 

Starting with tool Release 8.98.3 Oracle has supported Windows 2008 64bit platform to host JDEdwards EnterpriseOne web application over WebLogic 10.3.2 version. WebLogic is the core of Oracle Fusion Middleware architecture.

 

WebLogic typical installation put software on Windows 2008 server as application not as Windows Service. This article want to explain the command to execute to define WebLogic Admin Server, Nome Manager and JDEdwards web application components as Windows services.

 

 

 

 

 

How to configure NODE MANAGER

 

To install WebLogic Node Manager components as Windows service must be executed “installNodeMgrSvc.cmd” command file. This file is located under $WLS_HOME\server\bin\ (where WLS_HOME is directory where WebLogic is installed). On Windows 2008 to execute the command you must open a Windows command prompt as Administrator (using “Run as administrator” ).

 

 

 

 

 

How to configure ADMIN SERVER

 

 

 

Must be executeted these steps

 

1) Create directory “security” under E:\Oracle\Middleware\user_projects\domains\E1_Apps\servers\AdminServer

 

2) In this directory create a file named “boot.properties” and write in this file two variable user and password specified during WebLogic installation for example

 

username=weblogic

 

password=welcome1

 

When you’ll start Admin server as service these information will be automatically crypted

 

3) Create a command file and name it for example “installAdmServer_Service.cmd”. It’s not important where you’ll put it. Write these information into the file

 

SETLOCAL

 

set DOMAIN_NAME=E1_Apps (Domain created during WebLogic installation)

 

set USERDOMAIN_HOME=E:\Oracle\Middleware\user_projects\domains\E1_Apps

 

set SERVER_NAME=AdminServer

 

set PRODUCTION_MODE=true

 

cd %USERDOMAIN_HOME%

 

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

 

call "E:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc.cmd"

 

ENDLOCAL

 

4) Update file installsvc.cmd located under E:\Oracle\Middleware\wlserver_10.3\server\bin directory adding clause

 

-log:"E:\Oracle\Middleware\user_projects\domains\E1_Apps\AdminServer-stdout.txt"

 

To the command "%WL_HOME%\server\bin\beasvc" at the bottom of this file. This clause allow to generate log specifically for AdminServer application.

 

5) Execute installAdmServer_Service.cmd created at step 3 from a windows command prompt opened always with “Run As Administrator”

 

6) Compliments!!! You have installed WebLogic Admin server as Windows service!!!!

 

منقول من

http://www.j4jde.com/jde/34-cnc/98-weblogic-windows-service

 

شكرا جزيلا أخي على المجهود الرائع لكن لم أستطع تشغيل الفورم رغم أنني اتبعت خطواتك حرفيا

لا أدري أين المشكلة

أتمنى مزيدا من الشرح و شكرا

 

علما أن الخطأ الذي يظهر عند تشغيل الفورم هو

  Error 404--Not Found     From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:   10.4.5 404 Not Found  

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

أين الخلل؟