aplaws-devel — Developer Mailing List. Forum postings are forwarded to this list.

[Aplaws-devel] Metadata settings not visible for new content in Dec 5th Aplaws

[Steve H. <st...@ru...>]

Another question about the Dec 5th release - sent to Dan at RH
 directly but copying for the list again


----- Forwarded message -----

Hi Dan,
Just checked the install and we're not getting the meta-data section
 appearing for new content in the content-center - is this a
 mis-installation or has the feature been deprecated for something
 else? Can't see any errors when the pages are being created...
Thanks though!
 S.

----- End forwarded message -----


reply back was 


----- Forwarded message from "Daniel P. Berrange" -----

Do you mean the 'metadata' authoring kit step ? If so then that
is still to be integrated. Previously we could pre-integrate it
in the RPM, but now since we're distributing contenet types
separately from the 'dublinCore' application it needs to be
handled later.

Dan.

----- End forwarded message -----

[Aplaws-devel] Missing webapp path from the Dec 5th Aplaws release

[Steve H. <st...@ru...>]

Forwarding this to the list in case anyone else comes up against
 this - already got the solution from Dan at RH (attached at the
 end) which seems to do the trick
Anyway, hth!
 Steve

----- Forwarded message -----

Here's the description of the issue we are experiencing with 
 the Dec 5th Aplaws installation, namely

 SUMMARY:
	- Content for the front page of the Aplaws site is missing -
	  hitting the front page redirects to a non-existent directory

 ISSUES:
	- hitting home page of the installed site returns a 404
	  error, saying that 

		/ccm-ldn-portal/files/ was not found on this server.

	- Most of the other sections of the site work (admin pages,
 	  content-center, a-to-z, directory, services, sitemap) - 
	  news throws a java error regarding a missing method in an
	  existing class (less important for now)

	- ccm-ldn-portal package is installed according to the ccm
	  command, and all the webapp content from that package is
	  installed into the /usr/share/ccm/webapps/ROOT directory
	  (seems to be mostly gifs of content editing icons)

	- Only directories at the top of the /usr/share/ccm/webapps
	  directory are
	
		/ccm-ldn-atoz
		/ROOT
		/WEB-INF

	- Installation completed without errors, but we don't have
	  accurate installation instructions (due to changes since
	  the November release)

 SYSTEM:
	- Red Hat 8
	- IBM JDK 1.3.1
	- PostgreSQL 7.3.4
	- Resin 2.1.4
	
 INSTALLATION:

	Installation process we followed was

	+ download all of the rpms
	+ install all of the rpms on a fresh system 
	
		# rpm -ivh *.rpm

	+ create the postgres database
	+ re-source the profile file

		# . /etc/profile

	+ set up the page root and jdbc url

		# ccm load-aplaws --interactive --bundle /usr/share/ccm/aplaws-full.txt --parameter-file /usr/share/ccm/aplaws.properties --config

	+ copy in the oracle jdbc driver
	+ load the schema
		
		# ccm load-aplaws --interactive --bundle /usr/share/ccm/aplaws-full.txt --parameter-file /usr/share/ccm/aplaws.properties --recursive --schema

	+ load the data

		# ccm load-aplaws --interactive --bundle /usr/share/ccm/aplaws-full.txt --parameter-file /usr/share/ccm/aplaws.properties --recursive --data 

	+ ran ccm hostinit

		# ccm hostinit 

	+ manually added the port number to the resin.conf file
	+ started ccm

		# ccm start


----- End forwarded message -----


The response I got back from Dan at RedHat was the following 


----- Forwarded message from "Daniel P. Berrange" -----

Hi Steve,

I believe the issues you list below are caused by the missing
APLAWS web.xml file which defines the /ccm-ldn-portal/files
servlet mapping (and several others).

This can be resolved by setting the CCM_WEBXML environment
variable before running 'hostinit'. In addition to sort out
the missing resin port number you can supply 'http-port'
option. So in summary it would all look like:

  # export CCM_WEBXML=/usr/share/java/webapps/ccm-ldn-aplaws-1.9.1/ROOT/WEB-INF/
web.xml-aplaws
  # ccm hostinit http-port=8080

the requirement to set CCM_WEBXML is only a short term solution.
Ultimately 'ccm hostinit' will accept a bundle name as per the
'load' command which'll 'do the right' with the web.xml.

Dan.

------ End forwarded message -----

[Aplaws-devel] test

[Etherington, S. <ste...@ca...>]