Installing the BEA WebLogic Commerce Servers. including the Personalization Server and Commerce Server Components

Transcription

1 Istallig the BEA WebLogic Commerce Servers icludig the Persoalizatio Server ad Commerce Server Compoets BEA WebLogic Persoalizatio Server Documet Editio May 12, 2000

2 Copyright Copyright 2000 BEA Systems, Ic. All Rights Reserved. Restricted Rights Leged This software ad documetatio is subject to ad made available oly pursuat to the terms of the BEA Systems Licese Agreemet ad may be used or copied oly i accordace with the terms of that agreemet. It is agaist the law to copy the software except as specifically allowed i the agreemet. This documet may ot, i whole or i part, be copied, photocopied, reproduced, traslated, or reduced to ay electroic medium or machie-readable form without prior coset, i writig, from BEA Systems, Ic. Use, duplicatio or disclosure by the U.S. Govermet is subject to restrictios set forth i the BEA Systems Licese Agreemet ad i subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR ; subparagraph (c)(1)(ii) of the Rights i Techical Data ad Computer Software clause at DFARS , subparagraph (d) of the Commercial Computer Software--Licesig clause at NASA FAR supplemet ; or their equivalet. Iformatio i this documet is subject to chage without otice ad does ot represet a commitmet o the part of BEA Systems, Ic. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems, Ic. DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. Trademarks or Service Marks BEA, BEA Builder, BEA Jolt, BEA Maager, BEA MessageQ, BEA Tuxedo, BEA TOP END, BEA WebLogic, ad ObjectBroker are registered trademarks of BEA Systems, Ic. BEA elik, BEA esolutios, BEA TAP, BEA WebLogic Commerce Server, BEA WebLogic Eterprise, BEA WebLogic Express, BEA WebLogic Persoalizatio Server, BEA WebLogic Server, Java Eterprise Tuxedo, ad WebLogic Eterprise Coectivity are trademarks of BEA Systems, Ic. All other compay ames may be trademarks of the respective compaies with which they are associated. Istallig the BEA WebLogic Commerce Servers Documet Editio Date Software Versio 1.0 Jauary 2000 BEA WebLogic Commerce Servers February 2000 BEA WebLogic Commerce Servers April 2000 BEA WebLogic Commerce Servers May 12, 2000 BEA WebLogic Commerce Servers 2.0.1

3 Cotets About This Documet What You Need to Kow... vii e-docs Web Site... viii How to Prit the Documet... viii Cotact Us!... ix Documetatio Covetios...x 1. Preparig to Istall WebLogic Commerce Servers What s ew i WebLogic Commerce Servers Migratio Issues Overview of System Requiremets Platforms Memory Servers Databases Recommeded Istallatio Order Istallig BEA WebLogic Commerce Servers Licesig WebLogic Commerce Servers How WebLogic Commerce Servers licesig works How to reistall the WebLogicCommerceLicese.xml file by had Istallatio Istructios o Widows NT Istallatio Istructios o UNIX Istallatio Notes Where to Go Next Istallig the BEA WebLogic Commerce Servers iii

4 3. WebLogic Commerce Servers Cofiguratio Cofigurig Startup Files Cofigurig Properties Files Usig the Cloudscape database with WLCS Usig a Oracle database with WLCS Settig properties i the weblogic.properties file Settig the liste port Settig the password Settig the documet root Deployig EJBs Settig up coectio pools Settig up servlets ad ew portals Settig up the security realm for user maagemet Settig properties i the weblogiccommerce.properties file Settig up iteral values Settig up portals Settig up the RDBMS Realm Settig up user maagemet tables Settig up documetatio ame ad locatio Settig Up a Oracle Database Recreatig the Cloudscape Database Settig Up the Referece Implemetatio Documet Maagemet System (DMS) Istallig ad Cofigurig the WLCS/Iterwove TeamSite Iterface Istallig ad Cofigurig Documetum Documetum bea eviromet variables Example Applicatios Example Applicatios Portal Referece Implemetatio Notes Logi User/Group Creatio Default DB Realm Third Party Realms Cachig Properties iv Istallig the BEA WebLogic Commerce Servers

5 Repository Cosideratios Settig up a portal exampleportal Service Maager Etry Migratig to WLCS Portal Data Migratio Portlet defiitio Portal defiitio Persoalizatio Migratig Users User Idetificatio Movig Users Uique User Ids Migratig Groups Group Idetificatio Movig Groups Uique Group Ids Group-User Hierarchies Properties ad Property Sets JSP Migratio Sample Tables Retired Tags New Tags <um:logi> <um:getprofile> <um:getproperty> <um:setproperty> <um:removeproperty> <um:createuser> Istallig the BEA WebLogic Commerce Servers v

6 vi Istallig the BEA WebLogic Commerce Servers

7 About This Documet This documet explais how to istall the BEA WebLogic Commerce Servers icludig the Persoalizatio Server ad the Commerce Server Compoets. This documet covers the followig topics: Preparig to Istall WebLogic Commerce Servers: Pre-istallatio iformatio to uderstad whe istallig the system. Istallig BEA WebLogic Commerce Servers: The istallatio procedure for WebLogic Commerce Servers o NT ad supported UNIX systems. WebLogic Commerce Servers Cofiguratio: System cofiguratio iformatio. Example Applicatios: Sample portals that ship with WebLogic Commerce Servers Migratig to WLCS 2.0.1: Migratio iformatio for movig from WebLogic Commerce Servers 1.7 to What You Need to Kow This documet is iteded for busiess aalysts, Web developers, ad Web site admiistrators ivolved i settig up a ecommerce site usig BEA WebLogic Commerce Servers. It assumes a familiarity with the WebLogic Commerce Servers platform ad related Web techologies as described below. The topics i this documet are orgaized primarily aroud developmet goals ad the tasks eeded to accomplish them. Geerally, a set of topics also speaks to a particular developmet role ad requires the basic kowledge with regard to the techology focus of that role: Istallig the BEA WebLogic Commerce Servers vii

8 HTML author uses the Java Server Page (JSP) tags provide i the JSP tag library, thereby leveragig the power of persoalizatio without havig to kow Java. Java Server Page (JSP) developer creates JSPs usig the tags provided or by creatig custom tags as eeded. Applicatio assembler, system aalyst, or systems itegrator writes rules, writes, schemas, ad moitors usage. System admiistrator istalls, cofigures, deploys, ad moitors the Web applicatio server Java developer exted or modifies the Eterprise Java Bea (EJB) compoets that make up the Commerce Server egie, if that level of customizatio is eeded. e-docs Web Site BEA product documetatio is available o the BEA corporate Web site. From the BEA Home page, click o Product Documetatio or go directly to the e-docs Product Documetatio page at How to Prit the Documet You ca prit a copy of this documet from a Web browser, oe file at a time, by usig the File >Prit optio o your Web browser. A PDF versio of this documet is available o the WebLogic Commerce Servers documetatio Home page o the e-docs Web site (ad also o the documetatio CD). You ca ope the PDF i Adobe Acrobat Reader ad prit the etire documet (or a portio of it) i book format. To access the PDFs, ope the WebLogic Commerce Servers documetatio Home page, click the PDF files butto ad select the documet you wat to prit. viii Istallig the BEA WebLogic Commerce Servers

9 How to Prit the Documet If you do ot have the Adobe Acrobat Reader, you ca get it for free from the Adobe Web site at Cotact Us! Your feedback o the BEA WebLogic Commerce Servers documetatio is importat to us. Sed us at docsupport@bea.com if you have questios or commets. Your commets will be reviewed directly by the BEA professioals who create ad update the WebLogic Commerce Servers documetatio. I your message, please idicate that you are usig the documetatio for the BEA WebLogic Commerce Servers release. If you have ay questios about this versio of BEA WebLogic Commerce Servers, or if you have problems istallig ad ruig BEA WebLogic Commerce Servers, cotact BEA Customer Support through BEA WebSupport at You ca also cotact Customer Support by usig the cotact iformatio provided o the Customer Support Card, which is icluded i the product package. Whe cotactig Customer Support, be prepared to provide the followig iformatio: Your ame, address, phoe umber, ad fax umber Your compay ame ad compay address Your machie type ad authorizatio codes The ame ad versio of the product you are usig A descriptio of the problem ad the cotet of pertiet error messages Istallig the BEA WebLogic Commerce Servers ix

10 Documetatio Covetios The followig documetatio covetios are used throughout this documet. Covetio boldface text Ctrl+Tab italics moospace text moospace boldface text moospace italic text UPPERCASE TEXT Item Idicates terms defied i the glossary. Idicates that you must press two or more keys simultaeously. Idicates emphasis or book titles. Idicates code samples, commads ad their optios, data structures ad their members, data types, directories, ad file ames ad their extesios. Moospace text also idicates text that you must eter from the keyboard. Examples: #iclude <iostream.h> void mai ( ) the poiter psz chmod u+w * \tux\data\ap.doc tux.doc BITMAP float Idetifies sigificat words i code. Example: void commit ( ) Idetifies variables i code. Example: Strig expr Idicates device ames, eviromet variables, ad logical operators. Examples: LPT1 SIGNON OR x Istallig the BEA WebLogic Commerce Servers

11 Documetatio Covetios Covetio Item { } Idicates a set of choices i a sytax lie. The braces themselves should ever be typed. [ ] Idicates optioal items i a sytax lie. The brackets themselves should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list]... Separates mutually exclusive choices i a sytax lie. The symbol itself should ever be typed.... Idicates oe of the followig i a commad lie: That a argumet ca be repeated several times i a commad lie That the statemet omits additioal optioal argumets That you ca eter additioal parameters, values, or other iformatio The ellipsis itself should ever be typed. Example: buildobjcliet [-v] [-o ame ] [-f file-list]... [-l file-list] Idicates the omissio of items from a code example or from a sytax lie. The vertical ellipsis itself should ever be typed. Istallig the BEA WebLogic Commerce Servers xi

12 xii Istallig the BEA WebLogic Commerce Servers

13 1 Preparig to Istall WebLogic Commerce Servers Preparig to Istall WebLogic Commerce Servers icludes the followig topics: What s ew i WebLogic Commerce Servers Migratio Issues Overview of System Requiremets Platforms Memory Servers Databases Recommeded Istallatio Order What s ew i WebLogic Commerce Servers Persoalizatio Advisor: Persoalizatio Advisor recommeds cotet ad performs several importat fuctios i creatig a persoalized applicatio, icludig searchig for cotet, tyig the other core persoalizatio services together, ad matchig cotet to user profiles. Istallig the BEA WebLogic Commerce Servers 1-1

14 1 Preparig to Istall WebLogic Commerce Servers Property Set Maagemet: Property Set Maagemet allows you to create property sets, the schema of persoalizatio attributes, ad the properties that make up property sets. User Maagemet: User Maagemet jois eterprise data about users with profile data that is used to persoalize the users view of the applicatio. Cotet Maagemet: The Cotet Maagemet compoet provides cotet ad documet maagemet capabilities for use i persoalizatio services. You ca use the documet maagemet system (DMS) provided as a referece implemetatio with WLPS 2.0.1, or you ca use a third-party vedor s DMS, icludig Iterwove s TeamSite/OpeDeploy product ad Documetum s 4i product. Rules Maagemet: The Rules Maagemet compoet allows developers to create busiess rules that tur o ad off cotet ad match cotet to users accordig to user profile iformatio. Migratio Issues The WLCS istallatio will ot affect data i existig Portal 1.7 implemetatios. Refer to Migratig to WLCS o page 5-1 for more iformatio about migratio issues related to istallig WLCS with a existig Portal 1.7 istallatio. 1-2 Istallig the BEA WebLogic Commerce Servers

15 Overview of System Requiremets Overview of System Requiremets This sectio presets geeral iformatio about the WebLogic Commerce Servers system requiremets. For the latest platform updates ad versio-specific details, see the Supported Platforms sectio of the WebLogic Commerce Servers Release Notes. The Release Notes documet resides o the BEA "e-docs" Web site ad is updated periodically. For example, it is updated whe the WebLogic Commerce Servers software supports a additioal platform vedor ad operatig system. For our hardcopy readers, the URL of the Supported Platforms sectio is: Platforms BEA WebLogic Commerce Servers (WLCS) is available for Microsoft Widows NT systems ad various UNIX systems. For the latest details, see the Supported Platforms sectio of the WLCS Release Notes. For Widows NT, it is strogly recommeded that you be logged ito the PC as a user with admiistrative privileges prior to istallatio. Memory The product requires at least 128 MB of memory (RAM) to istall ad ru. The system will ru much better with more RAM, though. The istallatio requires the followig free disk space: 50 MB (Widows) 40 MB (UNIX) Istallig the BEA WebLogic Commerce Servers 1-3

16 1 Preparig to Istall WebLogic Commerce Servers Servers WLCS requires the followig software products: WebLogic Server 5.1 (SP1 for WLCS Compoets) Java 2 SDK 1.2. Differet Java 2 SDK 1.2.* versio levels are required for each platform. For the latest details, see the Supported Platforms sectio of the WLCS Release Notes. You must use at least JDK 1.2 to ru the example applicatios that ship with the product. Web browser (Iteret Explorer 4.0 ad above, or Netscape Commuicator 4.5 ad above) Text editor (such as Notepad, emacs, VI) Ratioal Rose 98i or 2000 required for use of the Rose Add-I, Rose UML, ad SmartGeerator (for the WLCS Compoets) For the latest details, see the Supported Platforms sectio of the WLCS Release Notes. Databases A DBMS ad a JDBC driver for the DBMS. This release has bee certified for Cloudscape ad Oracle databases. For the latest details about the supported database versio umbers ad drivers, see the Supported Platforms sectio of the WLCS Release Notes. A evaluatio versio of Cloudscape is distributed with the product as part of the example implemetatios. 1-4 Istallig the BEA WebLogic Commerce Servers

17 Recommeded Istallatio Order Recommeded Istallatio Order For a ew istallatio, BEA recommeds you istall the compoets i the followig order: 1. JDK 2. Ratioal Rose 3. WebLogic Server 4. WebLogic Commerce Servers (WLCS) Istallig the BEA WebLogic Commerce Servers 1-5

18 1 Preparig to Istall WebLogic Commerce Servers 1-6 Istallig the BEA WebLogic Commerce Servers

19 2 Istallig BEA WebLogic Commerce Servers Istallig BEA WebLogic Commerce Servers icludes the followig topics: Licesig WebLogic Commerce Servers How WebLogic Commerce Servers licesig works How to reistall the WebLogicCommerceLicese.xml file by had Istallatio Istructios o Widows NT Istallatio Istructios o UNIX Istallatio Notes Where to Go Next Licesig WebLogic Commerce Servers Whe you register to dowload WebLogic Commerce Servers (WLCS), you should also dowload a curret evaluatio licese. If you received the product o a disk, you will receive a licese file via to the accout specified o the purchase order. Istallig the BEA WebLogic Commerce Servers 2-1

20 2 Istallig BEA WebLogic Commerce Servers If you eed a ew evaluatio licese, revisit commerce.beasys.com, go through the dowload process, ad dowload oly the evaluatio licese. How WebLogic Commerce Servers licesig works WebLogic Commerce Servers licese keys are stored i WL_COMMERCE_HOME/licese i a file called WebLogicCommerceLicese.xml. This file must reside either i your workig directory or i a directory icluded i your WEBLOGIC_CLASSPATH. WLCS ships with the licese file i the CLASSPATH. If you have problems startig the server, we recommed you check the WL_COMMERCE_HOME\licese directory ad add the directory to your WEBLOGIC_CLASSPATH if ecessary. Movig the WebLogicCommerceLicese.xml file to a directory that is already i your CLASSPATH will also work. How to reistall the WebLogicCommerceLicese.xml file by had If you receive a ew WebLogicCommerceLicese.xml ad eed to reistall it, you should: 1. Delete ay old versios of WebLogicCommerceLicese.xml from your WEBLOGIC_CLASSPATH. 2. Verify that the WebLogicCommerceLicese.xml file is i your CLASSPATH or workig directory. The easiest approach is to keep your WebLogicCommerceLicese.xml i the WL_COMMERCE_HOME/licese directory ad esure this directory is i your WEBLOGIC_CLASSPATH. If you have two licese statemets for the same product i the file, oly the first oe will be used. 2-2 Istallig the BEA WebLogic Commerce Servers

21 Istallatio Istructios o Widows NT Istallatio Istructios o Widows NT 1. Start the istallatio by opeig the istallatio package, WLCS_201_NT4.exe. 2. Click through the Welcome ad Software Licese Agreemet screes. 3. I the Select your WebLogicCommerceLicese.xml scree, poit the wizard to the WebLogic Commerce Server licese (WebLogicCommerceLicese.xml) o your server. Click Next after you locate the licese file. 4. The IstallShield autodetects your JDK, WebLogic Server, ad Ratioal Rose istallatios. If it does t fid oe of those items, it asks you to poit to the directory that cotais it. Ratioal Rose is required for certai features i the Compoets, but it s ot required to ru the system. Refer to the Compoets documetatio for iformatio about usig Ratioal Rose with the Compoets. Istallig the BEA WebLogic Commerce Servers 2-3

22 2 Istallig BEA WebLogic Commerce Servers 5. I the Select Destiatio Directory scree, poit to the istallatio directory you wat to use. The default istallatio directory is \weblogiccommerce. Click Next. 6. After the istallatio completes, the BEA WebLogic Commerce Server has bee successfully istalled scree appears. 7. Ru StartCommerce.bat to start the Cloudscape versio of WebLogic Commerce Servers See Settig Up a Oracle Database o page 3-13 to ru WebLogic Commerce Servers with a database other tha the Cloudscape database that ships with the system. 2-4 Istallig the BEA WebLogic Commerce Servers

23 Istallatio Istructios o UNIX Istallatio Istructios o UNIX 1. Ujar the WLCS_201_UNIX.zip istallatio file i a directory. This process creates a directory called /WebLogicCommerce. 2. Chage to the /WebLogicCommerce directory ad ru istall.sh to create the startup files for WebLogic Commerce Servers. You eed to kow the locatio of the JDK ad WebLogic Server to complete the istallatio. 3. Make a licese directory at <istall-dir>/licese. 4. Copy your WebLogicCommerceLicese.xml file to the ew <istall-dir>/licese directory. 5. Ru StartCommerce.sh to start the Cloudscape versio of WebLogic Commerce Servers You may eed to chage file permissios to ru the script. Istallatio Notes WLCS ships with two supported database cofiguratios: Oracle ad Cloudscape. To eable easier deploymet of WLCS with these databases, BEA provides cofiguratio files for each database cofiguratio. The *-cmp files specify Cloudscape cofiguratio ad *-bmp files specify Oracle cofiguratio. You may eed to copy these files ito the default weblogic.properties ad weblogiccommerce.properties files, depedig o your database. Refer to Cofigurig Properties Files o page 3-3 for more iformatio about cofigurig the files. Istallig the BEA WebLogic Commerce Servers 2-5

24 2 Istallig BEA WebLogic Commerce Servers Where to Go Next 1. Chage to the istallatio directory ad start WLCS by ruig StartCommerce.bat (StartCommerce.sh for UNIX). The default istallatio path is \weblogiccommerce\startcommerce.bat or /weblogiccommerce/startcommerce.sh. You will see the cosole output i the cosole widow while the server iitializes. You will kow whe the server has fiished startig whe you see the message WebLogic Server started i the cosole output. This file defaults to the Cloudscape database. See Settig Up a Oracle Database o page 3-13 for iformatio about usig Oracle databases. 2. Usig a browser, try the example applicatios to make sure the server is workig correctly. The example applicatios use the Cloudscape database ad referece implemetatio DMS that ship with the system; therefore, you should ot have to make ay cofiguratio chages to test the system. All you eed to do is poit your browser to the correct URL listed for each applicatio below. Refer to WebLogic Commerce Servers Cofiguratio o page 3-1 for iformatio about makig cofiguratio chages to the system. You eed to chage cofiguratios if you use a database other tha Cloudscape or a DMS other tha the referece implemetatio DMS shipped with WLCS The cofiguratio documet also cotais iformatio about cofigurig other pieces of the system, icludig servlets ad portals. You might wat to leave the cosole widow i view whe testig the example applicatios. You ca see the cosole output idicatig that the server is hittig JSP pages, compilig the Java, ad takig care of other chores. Each page loads slowly the first time you access it because the Java compiler has to compile the page source code. Subsequet loads ad refreshes of the page go much faster tha the iitial load. The MyBuyBeas sample applicatio is icluded as a example of the WebLogic Commerce Servers power. The applicatio demostrates the commerce-based compoets of the system ad the persoalizatio services. You ca view the source i public_html/buybeas ad public_html/portals/buybeas. 2-6 Istallig the BEA WebLogic Commerce Servers

25 Where to Go Next To uderstad how directory structures relate to the URLs, refer to Settig up servlets ad ew portals o page 3-8. To ru the applicatio, poit your browser to /mpbb is a etry page for the MyBuyBeas portal that requires you to log i with a existig user. You ca hit to go directly to the MyBuyBeas portal without loggig i ad the create a ew user with the tools provided i the upper-right corer of the page. <port> is the ListePort of the ruig WebLogic Server set i the weblogic.properties file. The default value for ListePort is View the Acme Portal example at This portal demostrates fuctioality of the Portal Maagemet ad User Maagemet compoets. For persoalizatio admiistratio eeds, poit your browser to for the WebLogic Persoalizatio Server admiistratio tools. These tools allow you to create ad maage property sets, users, rules, ad portals. 3. Go through the tutorial that ships with the documetatio. The tutorial exteds the MyBuyBeas.com portal to iclude persoalizatio services for two differet user groups. 4. Begi buildig ad deployig your ow persoalized applicatios usig servlets or portals. Refer to the documetatio for more iformatio about usig the system. Istallig the BEA WebLogic Commerce Servers 2-7

26 2 Istallig BEA WebLogic Commerce Servers 2-8 Istallig the BEA WebLogic Commerce Servers

27 3 WebLogic Commerce Servers Cofiguratio WebLogic Commerce Servers Cofiguratio icludes the followig topics: Cofigurig Startup Files Cofigurig Properties Files Usig the Cloudscape database with WLCS Usig a Oracle database with WLCS Settig properties i the weblogic.properties file Settig properties i the weblogiccommerce.properties file Settig Up a Oracle Database Recreatig the Cloudscape Database Settig Up the Referece Implemetatio Documet Maagemet System (DMS) Istallig ad Cofigurig the WLCS/Iterwove TeamSite Iterface Istallig ad Cofigurig Documetum Documetum bea eviromet variables After istallig WebLogic Commerce Servers, you might eed to cofigure files, setup a database, set up the Documet Maagemet System (DMS), or perform other tweaks to the default istallatio. This documet describes the chages to make to cofigure the server. Istallig the BEA WebLogic Commerce Servers 3-1

28 3 WebLogic Commerce Servers Cofiguratio Most default settigs will work fie out of the box, especially if you ru the server with the Cloudscape database ad referece implemetatio DMS that ships with WLCS. If you use aother database or DMS or if you eed cofiguratio iformatio for settig up coectio pools, servlets, security, etc., this documet icludes cofiguratio iformatio for these tasks. Cofigurig Startup Files WLCS uses two files to set eviromet variables whe it starts the server: sethome.bat (sethome.sh for UNIX) ad StartCommerce.bat (StartCommerce.sh for UNIX). Use StartCommerce to start WLCS. StartCommerce.bat (StartCommerce.sh for UNIX) l This file starts the server. It calls sethome.bat or sethome.sh to cofigure the eviromet settigs ad the starts the server. You do t eed to make chages to the StartCommerce.bat or StartCommerce.sh file. sethome.bat (NT i <istall-dir>\bi\wi32) ad sethome.sh (UNIX systems i <istall-dir>/bi/solaris2) l This file cotais most of the eviromet settigs ad is called by the StartCommerce script. The istallatio program cofigures the settigs durig istallatio. You should ot have to chage it if you use the Cloudscape database that ships with WLCS If you have problems with the server startig, esure WL_COMMERCE_HOME is set to the directory that cotais the WLCS istall. Also esure the DB_CLASSPATH property poits to your database drivers ad the JDK_HOME poits to your JDK. All other settigs should work as shipped. 3-2 Istallig the BEA WebLogic Commerce Servers

29 Cofigurig Properties Files Cofigurig Properties Files This sectio cotais detailed referece iformatio for cofigurig the properties files for WLCS. The topics here discuss settig up coectio pools, servlets, ad portals, deployig EJBs, ad settig up security realms, i additio to other WLCS properties. To ru the Cloudscape database with the referece DMS that ships with the system, you should ot have to cofigure ay of the properties files here. The cofiguratio optios i this documet cover database setup iformatio for Oracle, DMS setup for Iterwove ad Documetum products, ad a variety of smaller topics relatig to Service Maager etries, realms, security, etc. The weblogic.properties ad weblogiccommerce.properties files that ship with the system have corollary files with cofiguratio iformatio for the Cloudscape ad Oracle databases. These corollary files, weblogic-cmp.properties ad weblogiccommerce-cmp.properties for Cloudscape ad weblogic-bmp.properties ad weblogiccommerce-bmp.properties for Oracle, cotai the default cofiguratio iformatio for each database. These stock files serve as templates for your weblogic.properties ad weblogiccommerce.properties files. The weblogic.properties ad weblogiccommerce.properties files that ship with the system cotai the default Cloudscape database cofiguratio iformatio that is also cotaied i the corollary files, weblogic-cmp.properties ad weblogiccommerce-cmp.properties files. If you use the Cloudscape database, you do t eed to edit the weblogic.properties ad weblogiccommerce.properties files. Usig the Cloudscape database with WLCS Out of the box, the weblogic.properties ad weblogiccommerce.properties files cotai the same iformatio as the weblogic-cmp.properties ad weblogiccommerce-cmp.properties sice the Cloudscape database rus the example applicatios. Istallig the BEA WebLogic Commerce Servers 3-3

30 3 WebLogic Commerce Servers Cofiguratio If you pla to use the Cloudscape database, you should ot eed to make modificatios to the weblogic.properties ad weblogiccommerce.properties files. Usig a Oracle database with WLCS If you use a Oracle database, edit the followig properties files, weblogic-bmp.properties ad weblogiccommerce-bmp.properties, the copy the files over the weblogic.properties ad weblogiccommerce.properties files. Basically, you eed to reame weblogic-bmp.properties ad weblogiccommerce-bmp.properties to weblogic.properties ad weblogiccommerce.properties ad make sure they re i the directory specified i the StartCommerce file (by default, the istallatio directory). This will eable WLCS to use a Oracle database istead of the default Cloudscape database. See Settig Up a Oracle Database o page 3-13 for more iformatio about cofigurig the databases. You also eed to chage DEPLOYMENT_SET=cmp to DEPLOYMENT_SET=bmp i sethome.bat. Settig properties i the weblogic.properties file The followig values eed to be set i the weblogic.properties file for the WebLogic Server istace to use as the host for the WLCS compoets. A weblogic.properties file is provided i the istallatio. Settig the liste port Look i the etry for the TCP/IP port umber i the weblogic.properties file i the Core System Properties sectio. You ca chage this value, ad the default is The default etry looks like the followig sippet: 3-4 Istallig the BEA WebLogic Commerce Servers

31 Cofigurig Properties Files # TCP/IP port umber at which the WebLogic Server listes for coectios weblogic.system.listeport=7601 Settig the password I the Core Security-Related Properties of weblogic.properties, the followig etry sets the userame ad password. Note that system is the userame ad weblogic is the password for the etry. You eed to eter these values whe usig the WLPS Admiistratio Tools at weblogic.password.system=weblogic Settig the documet root The documet root must be set to iclude pages for the admiistratio tools, portal pages, ad other pages to be accessible via the web server. For example, if you create create a ew portal, the its etries for homepage, workigdir, ad defaultdest will be relative to the documet root. weblogic.httpd.documetroot=/weblogiccommerce/server/public_html The documet root should be set correctly out of the box. This is the default locatio ad should ot chage uless you move the directory. Deployig EJBs The followig jar files must be icluded i the weblogic.ejb.deploy property value to properly deploy the WLCS beas. There is o eed for a drive specificatio if you re deployig jar files from the same file system of the <istall-dir>. However, if you wat to deploy jar files from aother file system, the you should specify the complete path. Example (istallatio directory file system): The first four jar files are differet for Cloudscape ad Oracle etries. Use the *-cmp jar files for Cloudscape deploymets. Istallig the BEA WebLogic Commerce Servers 3-5

32 3 WebLogic Commerce Servers Cofiguratio weblogic.ejb.deploy=\ /weblogiccommerce/lib/axiom-bmp-deploy.jar,\ /weblogiccommerce/lib/ebusiess-bmp-deploy.jar,\ /weblogiccommerce/lib/foudatio-bmp-deploy.jar,\ /weblogiccommerce/lib/examples-bmp-deploy.jar,\ /weblogiccommerce/lib/documet.jar,\ /weblogiccommerce/lib/usermgmt.jar,\ /weblogiccommerce/lib/bridge.jar,\ /weblogiccommerce/lib/foudatio.jar,\ /weblogiccommerce/lib/axiom.jar,\ /weblogiccommerce/lib/portal.jar,\ /weblogiccommerce/lib/ruleeditorbeas.jar,\ /weblogiccommerce/lib/rulesservice.jar,\ /weblogiccommerce/lib/schemamgr.jar,\ /weblogiccommerce/lib/p13advisor.jar Settig up coectio pools A JDBC jts pool, a typical JDBC coectio pool, ad a special coectio pool to support the cotet maagemet compoet must all be created to support the WLCS compoets. The followig examples provide a guidelie for settig up these pools. A developer eeds to adjust the pool properties to properties appropriate for the deploymet cofiguratio. Use weblogic-cmp.properties for Cloudscape ad weblogic-bmp.properties for Oracle ad copy the file over weblogic.properties. Example (usig Cloudscape): weblogic.jdbc.datasource.weblogic.jdbc.jts.commercepool= commercepool weblogic.jdbc.coectiopool.commercepool=\ url=jdbc:cloudscape:commerce,\ driver=com.cloudscape.core.jdbcdriver,\ iitialcapacity=5,\ maxcapacity=10,\ capacityicremet=1,\ props=user=test;password=test # Add a ACL for the coectio pool: weblogic.allow.reserve.weblogic.jdbc.coectiopool.commercepool= everyoe 3-6 Istallig the BEA WebLogic Commerce Servers

33 Cofigurig Properties Files # this is the pool the beas referece weblogic.jdbc.coectiopool.docpool=\ url=jdbc:beasys:docmgmt:com.beasys.commerce.axiom.documet.ref.re fdocumetprovider,\ driver=com.beasys.commerce.axiom.documet.jdbc.driver,\ logidelaysecs=1,\ iitialcapacity=1,\ maxcapacity=5,\ capacityicremet=1,\ allowshrikig=true,\ shrikperiodmis=15,\ refreshmiutes=10,\ props=jdbc.url=jdbc:weblogic:pool:commercepool;\ jdbc.ispooled=true;\ docbase=/weblogiccommerce/dmsbase/;\ schemaxml=/weblogiccommerce/dmsbase/doc-schema.xml weblogic.allow.reserve.weblogic.jdbc.coectiopool.docpool=every oe Example (usig Oracle): # Add a DataSource etry for JDBC coectios. You will the # referece it as: # Iitial Cotext iitcotext = ew IitialCotext(); # DataSource ds = # (javax.sql.datasource)iitcotext.lookup( weblogic.jdbc.jts. # commercepool ); weblogic.jdbc.datasource.weblogic.jdbc.jts.commercepool=commercep ool # I the etry below, server is hostame of database ad # TNSNAMES is the etry i tsames.ora # Example: url=jdbc:oracle:thi@moab:1521:teka weblogic.jdbc.coectiopool.commercepool=\ url=jdbc:oracle:thi:@server:port:tnsname,\ driver=oracle.jdbc.driver.oracledriver,\ iitialcapacity=5,\ maxcapacity=10,\ capacityicremet=1,\ props=user=test;password=test # Add a ACL for the coectio pool: weblogic.allow.reserve.weblogic.jdbc.coectiopool.commercepool= everyoe Istallig the BEA WebLogic Commerce Servers 3-7

34 3 WebLogic Commerce Servers Cofiguratio # Add a ACL for the coectio pool: weblogic.allow.reserve.weblogic.jdbc.coectiopool.jdbcpool=ever yoe If you use the com.beasys.commerce.axiom.cotact.security.rdbmsrealm class, settigs i the weblogiccommerce.properties file for the security realm must match these database settigs. Settig up servlets ad ew portals Leave the default etries for the demo portals ad servlets that ship with WLCS You oly eed to add etries for ew portals ad servlets. The PortalServiceMaager registratio for exampleportal below shows a example of how to register a portal; the specific parameters are described i the sectio o Creatig ad Maagig Portals. You should iclude the wlpsadmi tools etries directly. You ca view a table listig the valid PortalServiceMaager parameters ad values i the Creatig ad Maagig Portals sectio. I the etry below, ote the followig ame/value pairs: weblogic.httpd.register.exampleportal: URL of the portal or servlet. For example, The default ListePort value is portalame=exampleportal: Name of the portal assiged usig the Portal Maagemet admiistratio tool. homepage, defaultdest, ad workigdir locatios are relative to weblogic.httpd.documetroot Examples: weblogic.httpd.register.exampleportal=com.beasys.commerce.portal. admi.portalservicemaager weblogic.httpd.iitargs.exampleportal=\ portalame=exampleportal,\ homepage=/portals/example/portal.jsp,\ 3-8 Istallig the BEA WebLogic Commerce Servers

35 Cofigurig Properties Files defaultdest=/portals/example/portal.jsp,\ workigdir=/portals/example/,\ groupame=acmeusers,\ sessiocomparator=com.beasys.commerce.portal.admi.portalsessioc omparator,\ refreshworkigdir=120,\ repositorydir=/portals/repository/,\ timeout=99999,\ allowautologi=false weblogic.allow.execute.weblogic.servlet.wlpsadmi=system Settig up the security realm for user maagemet The weblogic.security.realmclass must be set to the appropriate WLCS class to hadle autheticatio ad to provide user ad group iformatio. It is ulikely a developer eeds to chage this value uless usig exteral sources such as LDAP. Example (i weblogiccommerce.properties): weblogic.security.realmclass=com.beasys.commerce.axiom.cotact. security.rdbmsrealm This is for the default realm oly. The RDBMSRealm properties must be set accordig to the database setup for the istallatio. A developer is likely to eed to adjust these values based o the deploymet cofiguratio. The example below shows etries for both Cloudscape ad Oracle. Note that the dburl must match that of the JDBC coectio pools as defied i the weblogiccommerce.properties file. Example (i weblogiccommerce.properties): # Cloudscape # commerce.usermgmt.rdbmsrealm.driver=com.cloudscape.core.jdbcdriver commerce.usermgmt.rdbmsrealm.dburl=jdbc:cloudscape:commerce;create=true;autocom mit=false commerce.usermgmt.rdbmsrealm.dbuser=oe commerce.usermgmt.rdbmsrealm.dbpassword=oe # Oracle # commerce.usermgmt.rdbmsrealm.driver=oracle.jdbc.driver.oracledriver commerce.usermgmt.rdbmsrealm.dburl=jdbc:oracle:thi:@server:port:tnsname Istallig the BEA WebLogic Commerce Servers 3-9

36 3 WebLogic Commerce Servers Cofiguratio commerce.usermgmt.rdbmsrealm.dbuser=test commerce.usermgmt.rdbmsrealm.dbpassword=test This is for the default realm oly. Settig properties i the weblogiccommerce.properties file Settig up iteral values The weblogiccommerce.properties file is used to set values for the WLCS compoets. A sample weblogiccommerce.properties file is icluded i the istallatio. These properties are used to set up values to be used iterally to idetify pools, classes, ad home ames. It is ulikely a developer would ever eed to chage these values, so these lies should remai uchaged. Example: commerce.jdbc.pool.ame=jdbcpool commerce.jts.pool.ame=commercepool commerce.schemagrouphomename.user=com.beasys.commerce.foudatio.property.schem a commerce.schemagrouphomename.request=com.beasys.commerce.foudatio.property.sc hema commerce.schemagrouphomename.session=com.beasys.commerce.foudatio.property.sc hema commerce.schemagrouphomename.content=com.beasys.commerce.axiom.documet.docume tschema commerce.home.p13.advisorhome=com.beasys.commerce.axiom.p13.advisor.persoali zatioadvisorhome commerce.home.rules.rulesservicehome=com.beasys.commerce.axiom.reasoig.rules. service.rulesservicehome commerce.home.property.schemamaagerhome=com.beasys.commerce.foudatio.propert y.schemamaager 3-10 Istallig the BEA WebLogic Commerce Servers

37 Cofigurig Properties Files Settig up portals The portal compoet has a umber of properties that it uses as defaults for whe a ew portal gets created. A developer might wat to adjust these values based o the ature of the portal beig built. The defaults ca be overridde usig the portal admiistratio tools. These portals will be copied from the weblogic.httpd.documetroot/<repository> directory ito the correspodig portal/ directories if they do ot exist already. Example: commerce.default.portal.headerurl=header.jsp commerce.default.portal.coteturl=portalcotet.jsp commerce.default.portal.footerurl=footer.jsp commerce.default.portal.cols=3 commerce.default.portal.suspededurl=suspeded.jsp commerce.default.portlet.dir=portlets/ commerce.default.portlet.image.dir=portlets/images/ commerce.default.portlet.titlebarurl=titlebar.jsp commerce.default.baer.color=# commerce.default.titlebar.bgcolor=# commerce.default.show.borders=false commerce.default.cotet.bgcolor=#cccccc commerce.default.titlebar.fot.color=#ffffff commerce.default.body.bgcolor=#ffffff commerce.default.portal.password=guest The followig property tells the portal compoet which property set to use as the default for portal users. A developer may wat to chage this value based o property sets created usig the Property Set Maagemet admiistratio tool. Example: commerce.default.portal.schemaname=_default_portal_schema The followig portal properties are for iteral use ad should ot be altered by a developer. Example: commerce.applicatio.miimum.build=57998 commerce.default.category.ame=home Istallig the BEA WebLogic Commerce Servers 3-11

38 3 WebLogic Commerce Servers Cofiguratio Settig up the RDBMS Realm If you eed to chage the settigs i the weblogiccommerce.properties file for the RDBMSRealm, chage the database settigs i a similar fashio to the database pools i weblogic.properties. Set the dbdriver, dburl, dbuser, ad dbpassword to use the same database that the commercepool uses i weblogic.properties. Settig up user maagemet tables The followig properties are used to idetify the iteral ames for tables for use by the user maagemet compoet. It is ulikely a developer would ever eed to chage these values. Example: commerce.usermgmt.usertable=wlcs_user commerce.usermgmt.grouptable=wlcs_group commerce.usermgmt.usergrouphierarchytable= WLCS_USER_GROUP_HIERARCHY commerce.usermgmt.grouphierarchytable=wlcs_group_hierarchy commerce.usermgmt.etityidtable=wlcs_entity_id commerce.usermgmt.profiletypetable=wlcs_unified_profile_type Settig up documetatio ame ad locatio The followig properties are used to set up the documetatio for the Persoalizatio Server compoets. Example: commerce.p13.documet.dev.ame=idex.html commerce.p13.documet.dev.versio=20 commerce.p13.documet.dev.docrootdir=docs 3-12 Istallig the BEA WebLogic Commerce Servers

39 Settig Up a Oracle Database Settig Up a Oracle Database For iformatio o the Oracle database ad driver that this release supports, see the Supported Platforms sectio of the WLCS Release Notes. For developmet ad productio purposes, WLCS requires a DBMS with specific database cofiguratios. This WLCS distributio icludes several SQL scripts that create the iitial database iformatio. You must have a JDBC driver ad have cofigured coectio pools (EJB) to access your database i the WebLogic Server. To create a ew Persoalizatio DBMS for Oracle databases: 1. Create a ew database user. 2. Make sure the user has all the ecessary permissios for creatig ad modifyig tables, idices, etc. 3. Log i to a SQL tool, such as SQL Worksheet, ad ru oe of the followig scripts, depedig o the cliet s operatig system. The scripts are located i <istall-dir>\db\oracle. For NT cliets, use create-p13-oracle-t.sql. For UNIX cliets, use create-p13-oracle-uix.sql. Note that if you use a remote database, the database host machie s operatig system does ot affect the script; you should ru the script that matches the cliet machie. The SQL scripts create the database schemas, icludig both the commerce tables ad persoalizatio tables, ad populate the tables with default data. However, the example applicatios (see Example Applicatios o page 4-1 for more iformatio) will ot work without completig Step 4 below to populate the remaider of the database. If the scripts are ot i the default directory, chage the path i <istall-dir>\db\oracle\createp13-oracle.sql to match the correct path. The just ru this file aloe ad referece the others. Istallig the BEA WebLogic Commerce Servers 3-13

40 3 WebLogic Commerce Servers Cofiguratio 4. Update the DB_CLASSPATH eviromet variable withi the sethome.bat (sethome.sh for UNIX) i the istallatio bi\wi32 (bi/solaris2 for UNIX systems) directory to iclude your JDBC database drivers. The DB_CLASSPATH is preset with hooks ito the Cloudscape database. To use a Oracle database, chage this eviromet variable to your DBMS JDBC database driver i sethome.bat or sethome.sh. The etry should be oe of the followig two etries: l l Cloudscape: SET DEPLOYMENT_SET=cmp Oracle: SET DEPLOYMENT_SET=bmp 5. Cofigure your database coectio pools. a. Ope the weblogic-bmp.properties file that resides i your istallatio directory. b. Chage the commercepool coectio properties to reflect your database cofiguratio. The properties file is preset with hooks ito the Cloudscape database. So chage the commercepool etries to reflect your database. For more iformatio o the JDBC pools, see Make sure you edit the appropriate *-cmp (Cloudscape) or *-bmp (Oracle) database cofiguratio files. Make sure you copy the Oracle file over the weblogic.properties file. c. Make the same chage i weblogiccommerce-bmp.properties ad the copy it over weblogiccommerce.properties. 6. Populate the remaider of the tables by performig the followig steps: a. Start WebLogic Server. b. Ru DataLoader.bat (<istall-dir>\bi\wi32 for NT) or DataLoader.sh (<istall-dir>/bi/solaris2 for UNIX systems) from the appropriate directory to populate the tables. c. Restart WebLogic Server Istallig the BEA WebLogic Commerce Servers

41 Recreatig the Cloudscape Database Recreatig the Cloudscape Database You might eed to recreate the default Cloudscape database if your Cloudscape database becomes corrupted or to clear out the curret tables. To recreate the database: 1. Ru BuyBeasDropCloudscape.sql to remove the buybeas tables from the database i the existig Cloudscape database. 2. To create the ew database, ru CloudscapeDatabaseCreator.bat (NT) or CloudscapeDatabaseCreator.sh (UNIX) i <istall-dir>\db\cloudscape. Settig Up the Referece Implemetatio Documet Maagemet System (DMS) This release ships with a default DMS usig the WLPS referece implemetatio. To idex cotet, the DMS uses the BulkLoader, a commad-lie utility that idexes all cotet uder the \dmsbase directory. Use the loaddocs.bat (NT) ad loaddocs.sh (UNIX) files to ru the BulkLoader. Refer to the Cotet Maagemet compoet documetatio for detailed iformatio about the commad-lie switches provided for the BulkLoader utility. See Istallig ad Cofigurig the WLCS/Iterwove TeamSite Iterface o page 3-16 for iformatio about usig Iterwove s TeamSite DMS ad see Istallig ad Cofigurig Documetum o page 3-20 for iformatio about usig the Documetum DMS. The demo database ships with the default cotet already idexed. For UNIX systems, chage sethome.sh ad loaddoc.sh files i <istall-dir>/bi/solaris2/ to cotai the paths to the istallatio directory. Istallig the BEA WebLogic Commerce Servers 3-15

42 3 WebLogic Commerce Servers Cofiguratio Istallig ad Cofigurig the WLCS/Iterwove TeamSite Iterface All cofiguratio documeted i this sectio applies to the Iterwove TeamSite Server. If you are ot usig Iterwove TeamSite for cotet maagemet, skip this cofiguratio procedure. Istallig ad cofigurig the WLCS iterface begis oly after successful istallatio of versio 4.2 of the TeamSite, TeamSite Templatig, Ope Deploy ad Data Deploy compoets, ad versio 5.1 of the WebLogic server ad versio 2.0 of the WebLogic Commerce Server. This icludes cofiguratio ad testig of the Data Deploy Automatio Server (DAS) compoet. The istallatio of the WLCS iterface ivolves the followig steps: 1. Istall the WLCS database server cliet iterface o the TeamSite server. The curret versio of the WLCS iterface executes o the TeamSite server ad may require certai compoets to be istalled to provide remote coectio with the WCLS database. This step is uecessary if the WLCS database ad TeamSite server are o the same platform. I additio, there may be eviromet variables that must be defied to allow a valid coectio. Refer to vedor documetatio for specific istallatio requiremets. 2. Modify the database coectio parameters to access the WLCS database. The DNR scripts, teamsite_wlcs_tras.ipl ad teamsite_wlcs.ipl, require a user id ad password for a accout with access to the WLCS database ad a valid Data Source Name (DSN) as defied by the Perl Data Base Iterface (DBI) stadard. The scripts are writte i Perl ad use the DBI iterface for accessig all databases both TeamSite ad WLCS. The coectio commad to the destiatio database must be modified to use these parameters to establish a coectio. This commad is idetified i each of the scripts as show below: # The followig is used to coect to the database. The format is: # DataSourceName, User, Password 3-16 Istallig the BEA WebLogic Commerce Servers

43 Istallig ad Cofigurig the WLCS/Iterwove TeamSite Iterface # Replace the hard-coded User ID ad Password (scott, tiger) with a valid accout # for the destiatio database. Replace the Data Source Name with a valid # specificatio for the destiatio database. The DSN is database specific. my $DES = DBI->coect("DBI:ODBC:ORAIWOV","scott","tiger", {RaiseError => 1} ); I the above example, the parameter scott would be replaced with a valid Oracle User Id, tiger would be replaced with the correspodig password, ad ORAIWOV would be replaced with a valid Data Source Name (DSN). The DSN is the most likely source of error. O NT residet databases, the easiest approach to defiig a valid DSN is to create a system DSN via the ODBC cotrol pael compoet. For a Uix database target the DSN is ormally the ame of the database server host, its listeig port (for example, Oracle uses 1521 as the default port umber), ad sometimes the database ame. For example, a Oracle database DSN could be specified: DBI:ODBC:<server host ame>:<port> If the target database platform provides a DBD driver that ca be istalled o the TeamSite server (cliet) the that driver ca be used istead of the ODBC DBD driver show above. For example: DBI:ORACLE:<server host ame>:<port> Refer to the vedor specific documetatio for the correct format of the DSN specificatio. The parameters used ca be tested usig the dbish utility provided with TeamSite Modify the TeamSite Data Deploy database coectio parameters. This step is optioal depedig o the TeamSite Data Deploy cofiguratio chose whe settig up the Data Deploy Automatio Server (DAS). The curret implemetatio does ot attempt to access those cofiguratio files to determie what optios were selected. The default cofiguratio uses the SQL Aywhere database that ships with TeamSite. This is also the cofiguratio that the DNR scripts use by default. Therefore, if all defaults were take, the the DNR script should require o modificatio. Please ote, however, that the SQL Aywhere licese provided with TeamSite oly supports a sigle coectio. This meas that multiple deploymets Istallig the BEA WebLogic Commerce Servers 3-17