Mastering BEA WebLogic Server Best Practices for Building and Deploying J2EE Applications [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Mastering BEA WebLogic Server Best Practices for Building and Deploying J2EE Applications [Electronic resources] - نسخه متنی

Gregory Nyberg, Robert Patricket al

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
توضیحات
افزودن یادداشت جدید






Installing WebLogic Server Software

The installation program packaged with WebLogic Server provides a straightforward way to install WebLogic Server on all required machines in the development environment. Follow the instructions in the program, and choose the default parameters and a Typical Installation unless you have a strong reason to customize the process.

When the installation process is complete, each machine will have a copy of WebLogic Server, but it will not yet have an empty domain to use for your application. You must create a Basic WebLogic Server Domain on each machine in the development environment using the Domain Configuration Wizard program. This program is available from the Start menu in Windows or may be started using the config script in the $WL_HOME/common/bin directory. The wizard program allows you to set up an empty domain quickly, using the Express Configuration option, or to customize the created domain using the Customized Configuration option. See the online Domain Configuration Wizard documentation at http://edocs.bea.com/wls/docs81/adminguide/createdomainl for detailed instructions.





Note

The bigrez.com application uses an empty Basic WebLogic Server Domain called “bigrezdomain” located in the /mastering/user_projects/ directory on each machine in the development environment. Server names, addresses, and ports use the default values, and the administrator username and password are system and insecure, respectively.


One final comment on hardware and software before we move on: Be sure to install WebLogic Server on the development servers in a manner consistent with your security and network rules. Never install WebLogic Server using the root account on a Unix machine, for example. Always create a weblogic or bea user account for this purpose and limit access to this account to certain developers or leads on the project. Create a weblogic group and make the weblogic user account a member of that group. Create additional developer accounts in the weblogic group and control their level of access to WebLogic Server files and directory structures using the standard permissions facilities of Unix.





Best Practice

Install WebLogic Server using a weblogic user account, not root. Create separate developer accounts in the weblogic group to provide limited developer access to WebLogic services and files.


/ 125