Hi Van, Thanks for writing that up. - Dave
On Mon, Mar 21, 2011 at 5:20 PM, Van Rogers-Ho <[email protected]> wrote: > Hi Dave, > > Here's the steps I used for deployment for WLS 11g. Recall that my > roller-custom.properties file is located in my war file and not in > classpath (I need to figure this one out still). > > > 1. roller-custom.properties - Fill environment specific configuration: > fill in LDAP > fill in mail info (refer to Jndi) > Roller-custom.properties, point to this jndi: > mail.configurationType=jndi > mail.jndi.name=mail/yourMailJNDIName > fill in DB info (refer to Jndi) > fill SSO info > fill in memcached settings > > > 2. Update planet-custom.properties > cache.dir=/your/roller-data/planet-cache > hibernate.dialect=org.hibernate.dialect.OracleDialect > > 3. Rebuild new war with updated roller-custom properties. > > 4. Memcached - > > * need ports opened. > * create dir your/memcached-rpm > * test by issuing: ./memcached-blogs restart from above directory > > > > WLS /Console Deployment > > > 5. EAR Deployment steps in console > 1. Cp ear roller.ear to MT install type directory. This directory > will also be referenced for future updates of EAR. > 2. Click Deployments under Domain Structure (Left hand menu) > 3. Provide path from step 1 in text box. Select "roller.ear" > next > 4. Select "Install this deployment as an application"> Next > 5. Select all targets>Next > 6. Provide name, "roller-weblogger" > Next > 7. Finish > > 6. Add DB source to JNDI > 1. Under Domain Structure, click Services>JDBC>Data Sources > 2. Click New > Name: Blogs Development. This is displayed when listing in WLS > JNDI Name: jdbc/somename > 3. Fill in Connection Properties > Fill in URL. Dev values are: "jdbc:oracle:thin:@localhost:1521:yourSID" > Database User Name: yourRollerUser > 4. Test connection > 5. Set target to deploy to > 6. Finish > > > > 7. Add mail sessions to JNDI > 1. Under Domain Structure, click Services>Mail Sessions > 2. Click New > 3. Fill in Name, JNDI name and properties. > > Name : Blogs > JNDI Name : mail/yourMailJNDIName > Fill in properties > 4. Set target to deploy to > 5. Finish > > > Hope that helps. > Van > > > > On Wed, Feb 16, 2011 at 1:52 PM, Dave <[email protected]> wrote: >> Hi Van, >> >> Sorry I missed your earlier email. roller-custom.properties is always >> supposed to be outside the WAR file. See section 8 of the install >> guide. Section 12 also gives some other options: >> >> # You can override the values in this file in a couple ways .. >> # 1. define a roller-custom.properties file and place it somewhere >> # at the root of one of your classpath locations. >> # for example: >> # $TOMCAT_HOME/common/classes >> # $ROLLER_LOCATION/WEB-INF/classes >> # >> # 2. specify a custom properties file via jvm option >> # example: >> # -Droller.custom.config=/path/to/properties/file >> >> Hope that helps... >> >> I think you have to use the -D option inside a WLS startup script, not sure >> tho. >> >> If you have time, please share with us what you had to do to make >> Roller 4.0.1 run on WebLogic 11, I have had no luck with WebLogic at >> all, with Roller 4 or 5. >> >> Thanks, >> - Dave >> >> >> >> On Wed, Feb 16, 2011 at 1:22 PM, Van Rogers-Ho <[email protected]> wrote: >>> Hi, >>> >>> Any guidance on this? >>> >>> Thanks, >>> Van >>> >>> On Fri, Jan 14, 2011 at 2:56 PM, Van Rogers-Ho <[email protected]> >>> wrote: >>>> Hi, >>>> >>>> I have a Roller 4.01 install up and running on a dev WLS 11g instance. >>>> It's all set up with connecting to Oracle db and mail via JNDI >>>> resources. The roller-custom.properties is in the WEB-INF/classes dir >>>> within the ear. What I'm hoping to do is pull the >>>> roller-custom.properties out of the ear and put it in a classpath >>>> outside of the war, say in WLS lib directory. Removing this would >>>> allow me to have a common ear that can be deployed across different >>>> environments (SSO, LDAP, DB, etc). >>>> >>>> However, Roller on deployment is not able to load the properties file. >>>> I've put multiple copies of the properties file in a few locations to >>>> see if one would get picked. Again, everything is fine if it is the >>>> roller EAR. >>>> >>>> I get the following in logs when deploying from WLS console, "Roller >>>> Weblogger: No custom properties file found in classpath." I believe >>>> this is coming from the WebloggerConfig class. >>>> >>>> Has anybody tried doing this type of deployment (EAR) on WLS with an >>>> external roller-custom.properties? >>>> >>>> Thanks, >>>> Van >>>> >>> >> >
