Web module problems in LR3

Hi,
I've been happily using LR1.3 for a while, exporting flash galleries from the 'web module' using SlideShowPro. I upgraded to LR3 last week, now when I go to the Web Module, none of the flash galleries work, not SSP, nor the simpleviewer etc. ones. I've removed the old LRwebengines and replaced with the latest LR3 one's for the relevent galleries, I've also updated the flash player, still no joy.
All the paremeter options show in the right hand pane for each of the galleries, but the main window is just black. The top left info panel briefly shows a 'copying resources' progress bar and then a 'task completed' message, but nothing shows in the main window.
Any ideas?
Edit, although the main preview screen is blank, I can export the gallery [certainly with SlideShowPro anyway] and the exported gallery is fine.

Yes the service ticket is still open. They have remoted to my computer. My last contact was that it was being sent up to Sr. Engineer. My problem goes away when I disable my wireless adapter. I think this weekend I will try hooking up to server with cable and see what happens. For now I am like you I use it by disabling the adapter then work on the galleries. Of coarse I can not push direct to my web site so I export to my desktop then us CuteFTP to up load. Like you this is a pain. I am still hoping they will find a fix. I have told them that I am not the only one having problem.
Hang in there.
Brad

Similar Messages

LR Web Module color management problem

I stumbled on to this discussion thread:
http://forums.adobe.com/message/3572174#3572174
initiated by “JimmysPhoto” because I have observed the same LR Web Module problem with images too saturated too much contrast and clipped highlights & shadows. Please note that this is not a settle difference, it’s a major change in the look of the image. I have a calibrated monitor using Spyder3 Elite. All other LR modules display the images exactly as I see in Development Module.
I did a test by exporting an image from the Dev Module to a file using the LR “Export “ function (from RAW to JPEG using sRBG color space) to a Windows file. When I display the image with the Windows Live Photo Gallery Viewer the image looks exactly the same as in the LR Dev module. However, opening this same image with IE-9 I get the same oversaturated look I see in the Web Module.
Because I use the LR Web Module to push photo galleries to my website host server I end up with images that do not look the way I processed them in LR – which is a serious issue for me. Was there any resolution to “JimmysPhoto” problems that I could benefit from?
I use Win7 64bit, LR 3.X and a high quality Dell U2410 display.

It's very strange that both IE9 and Chrome browsers go to the trouble of doing colour management, but both do it wrong - in different ways!
To colour-manage an image for display, you have to:
Figure out the profile of the image (often embedded in the image, or if none probably assume sRGB unless you know the image colour space by some other means)
Figure out the profile of the monitor (Windows will tell you that, if the monitor has a profile, otherwise you can't colour manage)
Using the two profiles, convert the image from the image colour space , via a Profile Connection Space (typically CIELAB (L*a*b*) or CIEXYZ), into the monitor's colour space.
The hard work is 3; finding out the profiles is easy.
IE9 does 1 and 3 but not 2. It goes to all the trouble of colour space conversion (step 3), but doesn't bother to look up the monitor profile. It assumes sRGB, which will be approximately right for most monitors, but never exactly right, and hopelessly wrong for wide gamut monitors.
Chrome does 2 and 3 but not 1. It goes to all the trouble of color space conversion, but doesn't bother to look up the image profile, assuming all images to be sRGB!
Why do the hard bit, but make a pig's ear of the easy bit?

Web Module Deployment Problem with Weblogic [Deployer:149026]

Dear Friends,
I've been facing a problem during deploying an Web Module on Weblogic 8.1. The name of my webmodule is 'MyOraWebModule'.
When I first developed, deployed and tested it in Weblogic 8.1, it was deployed and worked fine. But on the next day, when I tried to redeploy it, the deployment failed. This thing not just happens only once.. it is happeing always i.e. if I develop a new webmodule and deploy/redeploy it, it will work fine ONLY ON THE FIRST DAY (i.e. the day when the web module is created), but on the next day, it shows the following error if I try to redeploy it. The error is:
Task 3 failed: [Deployer:149026]Deploy application MyOraWebModule on myserver.
Deployment failed on Server myserver
Exception:weblogic.management.ApplicationException: prepare failed for MyOraWebModule
Module: MyOraWebModule Error: Context path 'MyOraWebModule' is already in use by the module: MyOraWebModule
Any suggestion or, guideline from you will be highly appreciated.
With Thanks,
... Chisty

Not sure if you are still looking for the answer. I have a similar problem, I have a work around on it but still trying to identify what the issue is. I have deployed multiple web application modules on weblogic 8.1 and on the redeploy I was gettig the exception weblogic.management.ApplicationException: prepare failed for USER_DEFINED_MODULE_NAME
Context path '/' is already in use by the module. when this exception is thrown I observed that the targets attribute of tag WebAppComponent is initialized to the server name. If I stop the server, make the value of the targets attribute to be empty string in config.xml and start the server, the server starts fine. And I could continue. Not sure why this is so since the targets attribute is used to identify on what servers the application needs to be deployed.
Any input on why the weblogic 8.1 is behaving this way when the targets attribute is defined with a value would of great help.
thanks,

LR3 Web module not loading pix of collection

Hi All,
I still have the same problem using the web module, which doesn't load all the pictures of the collection, and bugs. I never had this problem before using LR2. Does anybody encounter the same issue? Is there a way to fix this ?
Thanks for your help,
Sebastien

Resolved the problem.Found a tag missing from web.xml file.

Lightoom 3 web module FTP problems

I am at my wits end with the Lightroom 3 built in FTP. I have tried everything people have suggested to fix the problem with NO success. I am begging anyone out there who might know about the FTP program in Lightroom 3 to give me some suggestions on what I can do to fix this problem so I can update my website once again. I used to update my site weekly with the built in FTP inside the web module and then, for some unknown reason, it just stopped building the website. It seems to go through the whole export process only to get to the "building the website" portion and staying there for a long while until giving me this message. I have spent several hours with my ISP and my server host company and they insist it's not on their end. I've have tried every possible stratgy they suggest and still nothing! I know all my information is entered correctly. I've tried all the ports and even tried without the firewall. I use a Mac OS X with Snow Leopard with the updated version of Lightroom 3. I have tried uploading my website on several different ISP's and still nothing. Lightroom 3 is the only ftp that will not connect to my server. I would be sincerely grateful to whom ever may have a suggestion.
Thanks!

I have a suggestion. Transmit. I've never found Lightroom's FTP to be robust enough. It times out too quickly, and there's really not anything like the control from a dedicated FTP program.

Problem (un)Deploying Web Module on Root Context [/]

Hello all,
I have been attempting to deploy an EAR that has multiple web and ejb modules. All of the ejb modules deploy correctly and all but one of the web modules deploy correctly. The one that I am having problems with is the web module at the root context []. If the application server is already running when I try to deploy, I get the following error: (unimportant part removed)
INFO|javax.enterprise.system.container.web|WEB0113: Virtual server [server] already has a web module loaded at [/]; therefore web module [BlueCommerce:web-client.war] cannot be loaded at this context path on this virtual server.However, I have no module loaded at the root. I have also tried this on a newly created domain. Is there some default web module that I must remove first.
After the deploy fails, if I restart the application server I can access it, but all the security-constraints seem to be gone. Also, I cannot undeploy it without restarting the application server. When I attempt to do so, I get the following error:
SEVERE|javax.enterprise.system.container.web|[WebContainer] Undeployment fail for context /Any assistance would be appreciated. Thank you,
- Nathanael Law

The behaviour you are seeing is expected.
Notice that the container automatically defines and loads a default web
module with context root "/" if no such module has been defined among
the web modules and j2ee applications to be deployed on a virtual
server, and if the virtual server does not specify a
"default-web-module" attribute.
This default web module's docbase it set to the virtual server's docroot.
Therefore, in the case of the virtual server named "server", a default
web module with docbase SUNWappserver/domains/domain1/docroot is loaded
at the context root "/", which is why you see the index.html stored in
the above docbase when you access http://<host>:<non_admin_port>.
Once a web module has been deployed to a particular context root on a
virtual server, it cannot be overridden.
Jan

LR.3.3 Web module not picking up image edits

When I create a slideshow in LR3.3, it does not pick up the edits that I made to the images. The only things it picks up are crop and maybe sharpening (hard to tell). Haven't had the problem before today. Any help will be appreciated.
Thanks,
John

Pierluigi Vernetto, thanks for that link. Though it was for a web module consumption of the persistence package, I was able to adapt it for use by my ejb module.
Here is my solution, under split-directory development workflow.
Create the persistence module, place the persistence.xml in that module's META-INF.
Create an Ant task in the build.xml to 'wlcompile' and JAR it to the EAR direcotries APP-INF/lib directory.
Exclude the persistence module from the rest of the 'wlcompile' and 'appc' tasks.
I was then able to inject it with annotation in my EJB module.
dvohra16, thanks for that pointer. Now that I've been able to solve, the pressure is off (and shifted to other things). But I will surely check your option out. If I can get that working, it will be much easier than tinkering around with the build.xml and would be the normal flow of split-directory development workflow.
As of now, I will say this thread as 'solved', but if I get it working the way you mention (on my sandbox project), I will surely come back and update this thread.
Edited by: Vyoma on May 27, 2011 11:21 AM

Lightroom 3 Web module (Updated)

I've used Lightroom 3 in the past for uploading to my website with out a problem. Then, it seems at the same time as I uninstalled the trial version of CS5, my Lightroom 3 Web module would no longer upload to my website.
My inablity to upload information to my website has been going on for months. I have contacted my FTP host and they say there is nothing wrong on their side. I always check, re-check and re-re-check to make sure all my information is getting entered correctly. I have even taken classes on the use of Lightroom 3 to make sure I am not missing anything. When I attempt to upload the information, the exporting of files begins and it progresses all the way to "building the website" then stops after a few minutes and gives me this notice: "an error occurred sending the file: connection to the server failed". Can anyone please help? Should I reinstall the program? Will I lose all the information if I reinstall?
I should say that I'm running the latest version of Lightroom 3 on a Mac system OS X verson 10.6.8. Any thoughts are appreciated!
Message was edited by: Jase131

I have a similar problem. I've been using WSPP Impact, a LR3 plugin, to maintain a site with a gallery index page and 15 galleries. Addition of each gallery has been straightforward until now. But for the 16th gallery the WSPP publish service uploaded the photo files to my site server, but will not add the gallery index button to the index page. This ay be a problem or limitation with the WSPP Impact plugin, but I get no reply to requests for help to the author. Has anyone experience with this situation?

Web-module one step backwards

I am using the web-module for all my assigments, so this module is of great importance to me.
My galleries are created through TTG-templates and has been a breeeze to use. Unfortunately Adobe no longer support certain standards (I don't know the technial meaning of this) thus resultning my prewies are pretty lame in comparison to LR3.
On the other hand Adobe still supports the flash-galleries although flash, as I understanding, is a death path.
Mathhew from TTG pages has a longer discussion of these issues, including the technical buzz of which I understand nada , here: http://theturninggate.net/2012/01/lightroom-4-public-beta-ttg/
Brogaard - brogaard.com

BIG BIG problem with the new web module is that it doesn't offer any HTML5 galleries. By all means continue to offer the Flash galleries, but as we all know that Flash is going the way of the Dodo, we must see some HTML5 galleries so that people who use Apple products can actually see the galleries we create.
This really is important and I am surprised and astonished that Adobe haven't addressed this area.

Integrate a Web Module's JSP into an iView in NetWeaver CE 7.2

Hi everybody,
I am not sure whether this is the right spot to post this, but I will give it a try anyway.
We want to develop an Enterprise Application containing a Web Module. Basically it is a Java EE application that has a business tier consisting of a couple of beans and business objects and a web tier consisting of JSPs and servlets. What I want to do is to integrate it into the portal content via an iView. We only use a web module in order to integrate servlets to handle AJAX requests made via javascript and because you can only make a servlet-mapping within the web.xml (as far as I know).
Now I have created both the Enterprise Application Project as well as a Dynamic Web Project in the NWDS 7.2 according to the SAP manual. My servlet class as well as the beans are contained within the Dynamic Web Project's Java source folder. In the Web Content folder are the JSPs, css and javascript files. I deployed that application successfully via the NWDS and I can see under the application console of the NetWeaver Administrator that the application is deployed and alledgedly started, yet I cannot see it in the PCD. Therefore I cannot directly include it into a page and by that make it available to portal users. Also, I cannot access the application via the url http://<host>:<port>/<url as defined in application.xml>.
How can this be done?
Normally, I would do this by creating an iView from Template in the PCD's folder containing my designated page and role and adding it to the page as a deltalink. Yet when I try to do this, the portal offers me a long list of iView types, none of which seem to match my desire of matching a Web Module or Enterprise Application. Is that possible at all or what do I have to do to achieve this? I had no problem to integrate my application as a Portal Application, which is also deployed as an .ear, but that lacks the possibility to use servlets - at least from my understanding, since I cannot integrate a servlet-mapping into the portalapp.xml and there is no web.xml in a Portal Application.
I have been trying this for two days now and didn't succeed. Is it possible at all, and if so, how? Any help is highly appreciated!
Thanks in advance,
Serg

Hello,
You can use the j2ee telnet console and using it you can deploy the files
you can follow the example given in the note
743630 - How to deploy libraries on J2EE Engine 6.20
after ADD DEPLOY
DEPLOY <filename>.SCA
I hope this should work
Regards,
Chandru

Fix many web access problems with IFS 9.0.1 on Solaris (and other OS's)...

When the installation is done according to the documentation,
web access does not work because the scripts that add entries to
the jserv.properties file add duplicate references to
wrapper.env and wrapper.classpath. Look at the jserv.properties
file below and look at the remarked-out (#) lines of the
duplicate references. For example, look at the references to the
wrapper.env=LD_LIBRARY_PATH
Oracle, please note this bug so the web access problems are
minimized when the product is intstalled.
Thank you,
William T.
# Apache JServ Configuration
File #
################################ W A R N I N G
# Unlike normal Java properties, JServ configurations have some
important
# extensions:
# 1) commas are used as token separators
# 2) multiple definitions of the same key are concatenated in
a
# comma separated list.
# Execution parameters
# The Java Virtual Machine interpreter.
# Syntax: wrapper.bin=[filename] (String)
# Note: specify a full path if the interpreter is not visible in
your path.
wrapper.bin=/d3/Apache/jdk/bin/java
# Arguments passed to Java interpreter (optional)
# Syntax: wrapper.bin.parameters=[parameters] (String)
# Default: NONE
wrapper.bin.parameters=-Xms64m
wrapper.bin.parameters=-Xmx128m
# Apache JServ entry point class (should not be changed)
# Syntax: wrapper.class=[classname] (String)
# Default: "org.apache.jserv.JServ"
# Arguments passed to main class after the properties filename
(not used)
# Syntax: wrapper.class.parameters=[parameters] (String)
# Default: NONE
# Note: currently not used
# PATH environment value passed to the JVM
# Syntax: wrapper.path=[path] (String)
# Default: "/bin:/usr/bin:/usr/local/bin" for Unix systems
# "c:\(windows-dir);c:\(windows-system-dir)" for Win32
systems
# Notes: if more than one line is supplied these will be
concatenated using
# ":" or ";" (depending wether Unix or Win32) characters
# Under Win32 (windows-dir) and (windows-system-dir) will
be
# automatically evaluated to match your system
requirements
# CLASSPATH environment value passed to the JVM
# Syntax: wrapper.classpath=[path] (String)
# Default: NONE (Sun's JDK/JRE already have a default classpath)
# Note: if more than one line is supplied these will be
concatenated using
# ":" or ";" (depending wether Unix or Win32) characters.
JVM must be
# able to find JSDK and JServ classes and any utility
classes used by
# your servlets.
# Note: the classes you want to be automatically reloaded upon
modification
# MUST NOT be in this classpath or the classpath of the
shell
# you start the Apache from.
wrapper.classpath=/d3/Apache/jdk/lib/tools.jar
wrapper.classpath=/d3/Apache/Jserv/libexec/ApacheJServ.jar
wrapper.classpath=/d3/Apache/Jsdk/lib/jsdk.jar
# An environment name with value passed to the JVM
# Syntax: wrapper.env=[name]=[value] (String)
# Default: NONE on Unix Systems
# SystemDrive and SystemRoot with appropriate values on
Win32 systems
wrapper.env=PATH=/d3/bin
# An environment name with value copied from caller to Java
Virtual Machine
# Syntax: wrapper.env.copy=[name] (String)
# Default: NONE
# Uncomment the following lines to set the default locale and
NLS_LANG
# setting based on the environment variables.
# wrapper.env.copy=LANG
# wrapper.env.copy=NLS_LANG
# Copies all environment from caller to Java Virtual Machine
# Syntax: wrapper.env.copyall=true (boolean)
# Default: false
# Protocol used for signal handling
# Syntax: wrapper.protocol=[name] (String)
# Default: ajpv12
# General parameters
# Set the default IP address or hostname Apache JServ binds (or
listens) to.
# If you have a machine with multiple IP addresses, this address
# will be the one used. If you set the value to localhost, it
# will be resolved to the IP address configured for the locahost
# on your system (generally this is 127.0.0.1). This feature is
so
# that one can have multiple instances of Apache JServ listening
on
# the same port number, but different IP addresses on the same
machine.
# Use bindaddress=* only if you know exactly what you are doing
here,
# as it could let JServ wide open to the internet.
# You must understand that JServ has to answer only to Apache,
and should not
# be reachable by nobody but mod_jserv. So localhost is usually a
# good option. The second best choice would be an internal
network address
# (protected by a firewall) if JServ is running on another
machine than Apache.
# Ask your network admin.
# "*" may be used on boxes where some of the clients get
connected using
# "localhost"and others using another IP addr.
# Syntax: bindaddress=[ipaddress] or [localhost] or [*]
# Default: localhost
bindaddress=localhost
# Set the port Apache JServ listens to.
# Syntax: port=[1024,65535] (int)
# Default: 8007
port=8007
# Servlet Zones parameters
# List of servlet zones Apache JServ manages
# Syntax: zones=[servlet zone],[servlet zone]... (Comma
separated list of String)
# Default: NONE
zones=root
# Configuration file for each servlet zone (one per servlet zone)
# Syntax: [servlet zone name as on the zones list].properties=
[full path to configFile]
(String)
# Default: NONE
# Note: if the file could not be opened, try using absolute
paths.
root.properties=/d3/Apache/Jserv/etc/zone.properties
# Thread Pool parameters
# Enables or disables the use of the thread pool.
# Syntax: pool=true (boolean)
# Default: false
# WARNING: the pool has not been extensively tested and may
generate
deadlocks.
# For this reason, we advise against using this code in
production environments.
pool=false
# Indicates the number of idle threads that the pool may contain.
# Syntax: pool.capacity=(int)>0
# Default: 10
# NOTE: depending on your system load, this number should be low
for contantly
# loaded servers and should be increased depending on load
bursts.
pool.capacity=10
# Indicates the pool controller that should be used to control
the
# level of the recycled threads.
# Syntax: pool.controller=[full class of controller] (String)
# Default: org.apache.java.recycle.DefaultController
# NOTE: it is safe to leave this unchanged unless special
recycle behavior
# is needed. Look at the "org.apache.java.recycle" package
javadocs for more
# info on other pool controllers and their behavior.
pool.controller=org.apache.java.recycle.DefaultController
# Security parameters
# Enable/disable the execution of org.apache.jserv.JServ as a
servlet.
# This is disabled by default because it may give informations
that should
# be restricted.
# Note that the execution of Apache JServ as a servlet is
filtered by the web
# server modules by default so that both sides should be enabled
to let this
# service work.
# This service is useful for installation and configuration
since it gives
# feedback about the exact configurations Apache JServ is using,
but it should
# be disabled when both installation and configuration processes
are done.
# Syntax: security.selfservlet=true (boolean)
# Default: false
# WARNING: disable this in a production environment since may
give reserved
# information to untrusted users.
security.selfservlet=true
# Set the maximum number of socket connections Apache JServ may
handle
# simultaneously. Make sure your operating environment has
enough file
# descriptors to allow this number.
# Syntax: security.maxConnections=(int)>1
# Default: 50
security.maxConnections=50
# Backlog setting for very fine performance tunning of JServ.
# Unless you are familiar to sockets leave this value commented
out.
# security.backlog=5
# List of IP addresses allowed to connect to Apache JServ. This
is a first
# security filtering to reject possibly unsecure connections and
avoid the
# overhead of connection authentication.
# <warning>
# (please don't use the following one unless you know what you
are doing :
# security.allowedAddresses=DISABLED
# allows connections on JServ'port from entire internet.)
# You do need only to allow YOUR Apache to talk to JServ.
# </warning>
# Default: 127.0.0.1
# Syntax: security.allowedAddresses=[IP address],[IP Address]...
(Comma
separated list of IP addresses)
#security.allowedAddresses=127.0.0.1
# Enable/disable connection authentication.
# NOTE: unauthenticated connections are a little faster since
authentication
# handshake is not performed at connection creation.
# WARNING: authentication is disabled by default because we
believe that
# connection restriction from all IP addresses but localhost
reduces your
# time to get Apache JServ to run. If you allow other addresses
to connect and
# you don't trust it, you should enable authentication to
prevent untrusted
# execution of your servlets. Beware: if authentication is
disabled and the
# IP address is allowed, everyone on that machine can execute
your servlets!
# Syntax: security.authentication=[true,false] (boolean)
# Default: true
security.authentication=false
# Authentication secret key.
# The secret key is passed as a file that must be kept secure
and must
# be exactly the same of those used by clients to authenticate
themselves.
# Syntax: security.secretKey=[secret key path and filename]
(String)
# Default: NONE
# Note: if the file could not be opened, try using absolute
paths.
#security.secretKey=./etc/jserv.secret.key
# Length of the randomly generated challenge string (in bytes)
used to
# authenticate connections. 5 is the lowest possible choice to
force a safe
# level of security and reduce connection creation overhead.
# Syntax: security.challengeSize=(int)>5
# Default: 5
#security.challengeSize=5
# Logging parameters
# Enable/disable Apache JServ logging.
# WARNING: logging is a very expensive operation in terms of
performance. You
# should reduced the generated log to a minumum or even disable
it if fast
# execution is an issue. Note that if all log channels (see
below) are
# enabled, the log may become really big since each servlet
request may
# generate many Kb of log. Some log channels are mainly for
debugging
# purposes and should be disabled in a production environment.
# Syntax: log=[true,false] (boolean)
# Default: true
log=true
# Set the name of the trace/log file. To avoid possible
confusion about
# the location of this file, an absolute pathname is recommended.
# This log file is different than the log file that is in the
# jserv.conf file. This is the log file for the Java portion of
Apache
# JServ.
# On Unix, this file must have write permissions by the owner of
the JVM
# process. In other words, if you are running Apache JServ in
manual mode
# and Apache is running as user nobody, then the file must have
its
# permissions set so that that user can write to it.
# Syntax: log.file=[log path and filename] (String)
# Default: NONE
# Note: if the file could not be opened, try using absolute
paths.
log.file=/d3/Apache/Jserv/logs/jserv.log
# Enable the timestamp before the log message
# Syntax: log.timestamp=[true,false] (boolean)
# Default: true
log.timestamp=true
# Use the given string as a data format
# (see java.text.SimpleDateFormat for the list of options)
# Syntax: log.dateFormat=(String)
# Default: [dd/MM/yyyy HH:mm:ss:SSS zz]
log.dateFormat=[dd/MM/yyyy HH:mm:ss:SSS zz]
# Since all the messages logged are processed by a thread
running with
# minimum priority, it's of vital importance that this thread
gets a chance
# to run once in a while. If it doesn't, the log queue overflow
occurs,
# usually resulting in the OutOfMemoryError.
# To prevent this from happening, two parameters are used:
log.queue.maxage
# and log.queue.maxsize. The former defines the maximum time for
the logged
# message to stay in the queue, the latter defines maximum
number of
# messages in the queue.
# If one of those conditions becomes true (age > maxage || size
maxsize),# the log message stating that fact is generated and the log
queue is
# flushed in the separate thread.
# If you ever see such a message, either your system doesn't
live up to its
# expectations or you have a runaway loop (probably, but not
necessarily,
# generating a lot of log messages).
# WARNING: Default values are lousy, you probably want to tweak
them and
# report the results back to the development team.
# Syntax: log.queue.maxage = [milliseconds]
# Default: 5000
log.queue.maxage = 5000
# Syntax: log.queue.maxsize = [integer]
# Default: 1000
log.queue.maxsize = 1000
# Enable/disable logging the channel name
# Default: false
# log.channel=false
# Enable/disable channels, each logging different actions.
# Syntax: log.channel.[channel name]=[true,false] (boolean)
# Default: false
# Info channel - quite a lot of informational messages
# hopefully you don't need them under normal circumstances
# log.channel.info=true
# Servlets exception, i.e. exception caught during
# servlet.service() processing are monitored here
# you probably want to have this one switched on
log.channel.servletException=true
# JServ exception, caught internally in jserv
# we suggest to leave it on
log.channel.jservException=true
# Warning channel, it catches all the important
# messages that don't cause JServ to stop, leave it on
log.channel.warning=true
# Servlet log
# All messages logged by servlets. Probably you want
# this one to be switched on.
log.channel.servletLog=true
# Critical errors
# Messages produced by critical events causing jserv to stop
log.channel.critical=true
# Debug channel
# Only for internal debugging purposes
# log.channel.debug=true
#wrapper.classpath=/d3/ord/jlib/ordim.zip
#wrapper.classpath=/d3/ord/jlib/ordhttp.zip
# Oracle XSQL Servlet
wrapper.classpath=/d3/lib/oraclexsql.jar
# Oracle JDBC
wrapper.classpath=/d3/jdbc/lib/classes12.zip
# Oracle XML Parser V2 (with XSLT Engine)
wrapper.classpath=/d3/lib/xmlparserv2.jar
# Oracle XML SQL Components for Java
wrapper.classpath=/d3/rdbms/jlib/xsu12.jar
# XSQLConfig.xml File location
wrapper.classpath=/d3/xdk/admin
# Oracle BC4J
wrapper.classpath=/d3/ord/jlib/ordim.zip
wrapper.classpath=/d3/ord/jlib/ordvir.zip
wrapper.classpath=/d3/ord/jlib/ordhttp.zip
wrapper.classpath=/d3/BC4J/lib/jndi.jar
wrapper.classpath=/d3/BC4J/lib/jbomt.zip
wrapper.classpath=/d3/BC4J/lib/javax_ejb.zip
wrapper.classpath=/d3/BC4J/lib/jdev-rt.jar
wrapper.classpath=/d3/BC4J/lib/jbohtml.zip
wrapper.classpath=/d3/BC4J/lib/jboremote.zip
wrapper.classpath=/d3/BC4J/lib/jdev-cm.jar
wrapper.classpath=/d3/BC4J/lib/jbodomorcl.zip
wrapper.classpath=/d3/BC4J/lib/jboimdomains.zip
wrapper.classpath=/d3/BC4J/lib/collections.jar
wrapper.classpath=/d3/Apache/Apache/htdocs/onlineorders_html
#wrapper.classpath=/d3/Apache/Apache/htdocs/OnlineOrders_html/Onl
ineOrders.jar
# The following classpath entries are necessary for EJBs to run
in IAS or DB when
present
wrapper.classpath=/d3/lib/aurora_client.jar
wrapper.classpath=/d3/lib/vbjorb.jar
wrapper.classpath=/d3/lib/vbjapp.jar
# Oracle Servlet
wrapper.classpath=/d3/lib/servlet.jar
# Oracle Java Server Pages
wrapper.classpath=/d3/jsp/lib/ojsp.jar
# Oracle Util
wrapper.classpath=/d3/jsp/lib/ojsputil.jar
# Oracle Java SQL
wrapper.classpath=/d3/sqlj/lib/translator.zip
# Oracle JDBC
#wrapper.classpath=/d3/jdbc/lib/classes12.zip
# SQLJ runtime
wrapper.classpath=/d3/sqlj/lib/runtime12.zip
# Oracle Messaging
wrapper.classpath=/d3/rdbms/jlib/aqapi.jar
wrapper.classpath=/d3/rdbms/jlib/jmscommon.jar
# OJSP environment settings
#wrapper.env=ORACLE_HOME=/d3
# The next line should be modified to reflect the value of the
SID for your
webserver.
#wrapper.env=ORACLE_SID=cmpdb
#wrapper.env=LD_LIBRARY_PATH=/d3/lib
## Enable the flag below if you are using jdk 1.2.2_05a or above
#wrapper.env=JAVA_COMPILER=NONE
# Advanced Queuing - AQXML
wrapper.classpath=/d3/rdbms/jlib/aqxml.jar
#wrapper.classpath=/d3/rdbms/jlib/xsu12.jar
#wrapper.classpath=/d3/lib/xmlparserv2.jar
wrapper.classpath=/d3/lib/xschema.jar
#wrapper.classpath=/d3/jlib/jndi.jar
wrapper.classpath=/d3/jlib/jta.jar
oemreporting.properties=/d3/Apache/Jserv/oemreporting/oemreportin
g.properties
zones = root, oemreporting
wrapper.classpath=/d3/jlib/share-opt-1_1_9.zip
wrapper.classpath=/d3/jlib/caboshare-opt-1_0_3.zip
wrapper.classpath=/d3/jlib/marlin-opt-1_0_7.zip
wrapper.classpath=/d3/jlib/tecate-opt-1_0_4.zip
wrapper.classpath=/d3/jlib/ocelot-opt-1_0_2.zip
wrapper.classpath=/d3/jlib/regexp.jar
wrapper.classpath=/d3/jlib/sax2.jar
#wrapper.classpath=/d3/jlib/servlet.jar
wrapper.bin.parameters= -DORACLE_HOME=/d3
#wrapper.env=LD_LIBRARY_PATH=/d3/lib32
wrapper.env.copy=DISPLAY
wrapper.bin.parameters=-DORACLE_HOME=/d3
#wrapper.classpath=/d3/lib/vbjorb.jar
#wrapper.classpath=/d3/lib/vbjapp.jar
wrapper.classpath=/d3/classes/classesFromIDLVisi
wrapper.classpath=/d3/jlib/swingall-1_1_1.jar
wrapper.classpath=/d3/jlib/ewtcompat3_3_15.jar
wrapper.classpath=/d3/jlib/ewt-3_3_18.jar
wrapper.classpath=/d3/jlib/share-1_1_9.jar
wrapper.classpath=/d3/jlib/help-3_2_9.jar
wrapper.classpath=/d3/jlib/ice-5_06_3.jar
wrapper.classpath=/d3/jdbc/lib/classes111.zip
wrapper.classpath=/d3/classes
wrapper.classpath=/d3/jlib/oembase-9_0_1.jar
wrapper.classpath=/d3/jlib/oemtools-9_0_1.jar
wrapper.classpath=/d3/jlib
wrapper.classpath=/d3/jlib/javax-ssl-1_1.jar
wrapper.classpath=/d3/jlib/jssl-1_1.jar
wrapper.classpath=/d3/jlib/netcfg.jar
wrapper.classpath=/d3/jlib/dbui-2_1_2.jar
#wrapper.classpath=/d3/lib/aurora_client.jar
#wrapper.classpath=/d3/lib/xmlparserv2.jar
wrapper.classpath=/d3/network/jlib/netmgrm.jar
wrapper.classpath=/d3/network/jlib/netmgr.jar
wrapper.classpath=/d3/network/tools
wrapper.classpath=/d3/jlib/kodiak-1_2_1.jar
wrapper.classpath=/d3/sysman/jlib/netchart360.jar
wrapper.classpath=/d3/jlib/pfjbean.jar
wrapper.env=SHLIB_PATH=/d3/lib32
wrapper.env=LIBPATH=/d3/lib32
wrapper.classpath=/d3/ultrasearch/lib/isearch_midtier.jar
wrapper.classpath=/d3/ultrasearch/lib/isearch_query.jar
wrapper.classpath=/d3/ultrasearch/lib/jgl3.1.0.jar
wrapper.classpath=/d3/lib/mail.jar
wrapper.classpath=/d3/lib/activation.jar
wrapper.classpath=/d3/ultrasearch/jsp/admin/config
# Additions for iFS
## DO NOT REMOVE OR ALTER THE FOLLOWING LINE ....
# iFS true
# Uncomment if you want to use the same Jserv as other
applications
wrapper.classpath=/d3/9ifs/custom_classes
wrapper.classpath=/d3/9ifs/settings
wrapper.classpath=/d3/9ifs/lib/adk.jar
wrapper.classpath=/d3/9ifs/lib/email.jar
wrapper.classpath=/d3/9ifs/lib/http.jar
wrapper.classpath=/d3/9ifs/lib/release.jar
wrapper.classpath=/d3/9ifs/lib/repos.jar
wrapper.classpath=/d3/9ifs/lib/utils.jar
wrapper.classpath=/d3/9ifs/lib/webui.jar
wrapper.classpath=/d3/9ifs/lib/provider.jar
wrapper.classpath=/d3/jlib/javax-ssl-1_2.jar
wrapper.classpath=/d3/jlib/jssl-1_2.jar
wrapper.env=ORACLE_HOME=/d3
wrapper.env=ORACLE_SID=cmpdb
wrapper.env=LD_LIBRARY_PATH=/d3/lib:/d3/ctx/lib:/d3/lib32
wrapper.env=NLS_LANG=.US7ASCII
## Additions for the iFS zone
# Uncomment if you want to use the same Jserv as other
applications
zones=ifs
ifs.properties=/d3/Apache/Jserv/etc/ifs.properties
# End iFS section

About your home page; Manually set up Firefox with the window(s) and tab(s)
the way you want them to be. Then;
'''''Firefox Options > General > Homepage'''''.
Press the button labeled ''''Use Current'''.'
=====================================
Open a new window or tab. In the address bar, type '''''about:config'''''.
If a warning screen comes up, press the '''''Be Careful''''' button.
This is where Firefox finds information it needs to run.
At the top of the screen is a search bar. Enter '''''browser.newtab.url'''''
and press enter. '''''browser.newtab.url'''''
tells Firefox what to show when a new tab is opened.
If you want, right click and select '''''Modify'''''. You can change the
setting to; about:home (Firefox default home page), 
about:newtab (shows the sites most visited), 
about:blank (a blank page), 
or you can enter any web page you want. 
The same instructions are used for the new window setting, listed as
'''''browser.startup.homepage'''''.

Error in running a URL for Web Module Project with a JSP

Hi Experts,
I created a Web Module Project with name "WebModuleProject".
I created a jsp file naming "test_jsp" inside it
Then i created a Web Archive for it which resulted in a WebModuleProject.war file.
I then created an Enterprise Module Project with name "EnterpriseWebModule"
Then i linked the "WebModuleProject" whith this project.
I created an EAR for this project.
Deployed that EAR on to hte J2EE Engine.
Now on applying the following url:
<a href="http://server:port/WebModuleProject/test_jsp.jsp">http://server:port/WebModuleProject/test_jsp.jsp</a>
i m getting the following error
404 Not Found
The requested resource /WebModuleProject/test_jsp.jsp is not available
Details: File [WebModuleProject/test_jsp.jsp] not found in application root of alias [/] of J2EE application [sap.com/com.sap.engine.docs.examples].
Please experts help me to dig out this problem
Can anybody suggest me why i m getting this error? And how to resolve it???????

Hi Saurabh,
In SMICM transaction code we have to maintain the parameters in order to run the web report in the specified format.
i am listing some parameters in the below, Please have a look and see whether it can help u out .....
Services
icm/server_port_0 = PROT=HTTP,PORT=8000
icm/server_port_1 = PROT=SMTP,PORT=0
HTTP settings
icm/HTTP/max_request_size_KB = 102400
icm/HTTP/j2ee_0 = PREFIX=/,HOST=localhost,CONN=0-500,PORT=50000
icm/HTTP/server_cache_0 = PREFIX=/, CACHEDIR=/usr/sap/BSD/DVEBMGS00/dat
 a/cache
Misc
icm/host_name_full = cauvery.com
icm/cancel_strategy = cancel requests without session (stateless)
rdisp/plugin_auto_logout = 1800
is/HTTP/virt_host_0 = :;
is/SMTP/virt_host_0 = :;
Once after maintain the parameters go and check in the SICF transaction code SAPBW---BEx + right click + test service. And check whether it is opening in the required URL path.
Regards,
Vara Prasad.

Error on deploying JSP web module

Hi,
I've created a JSP web module that consumes a web service. I'm following this tutorial
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0cf9e42-ccb0-2c10-d0a4-f5aa8a79e19a?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0cf9e42-ccb0-2c10-d0a4-f5aa8a79e19a?quicklink=index&overridelayout=true]
But when I deploy my ear project, I had this error
Application error occurred during the request procession.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
Error compiling [/sample.jsp] of alias [LocalDevelopmentdc_webmodulesap.com] of J2EE application [sap.com/dc_webmoduleear].
Exception id: [001CC43ABAC00086000056FB00006CEA0004A5A7E1A64FD3]
Here's the java code in the JSP:
InitialContext ctx = new InitialContext();
WS_Preview obj = (WS_Preview).ctx.lookup("java:comp/env/newproxy");
WS_PreviewViDocument port = (WS_PreviewViDocument)obj.getLogicalPort("Config1Port_Document",WS_PreviewViDocument.class);
GetElementXHTMLValueResponse result = new GetElementXHTMLValueResponse();
result = port.GetElementXHTMLValue("A","A","A");
out.print(result);
Does anyone know how to solve this error? Thanks

Because you do not have an infrastructure database, you will not be able to deploy your web service from OEM as one of its steps is to register the service in the UDDI registy - the Web service deployment and UDDI registration are tied tightly together in OEM right now.
All is not lost, however. You have two routes to deploy the Web Service on Oracle9iAS:
1. Use DCM, which is the command line interface to deploy applications/webservices/wars/ears on Oracle9iAS. It does not have the dependency on UDDI.
To deploy a Web service using DCM, say your Web service ear file were named test.ear your deployment command would look something like:
c:\oracle\ora903\dcm\bin\dcmctl deployApplication -file test.ear
See the doc for much more detail to let you tailor DCM to do all the stuff that is available through EM or specific to your application:
http://download-west.oracle.com/docs/cd/A97329_03/core.902/a92171/dcm.htm#643834
2. In JDeveloper 9.0.3, there is a DCM Servlet that lets you do remote deployment to Oracle9iAS:
http://otn.oracle.com/products/jdev/htdocs/readme_9031.html#viadcm
I suspect your deployment problem from Oracle9i JDeveloper may be (this may be an incorrect assumption) due to trying to use a connection that is setup as if Oracle9iAS is a standalone OC4J.
Mike.

Content in a Web Module

Hi,
I am having a very irritating problem. I want to use a filter to transform some content however I do not want the content to have to be inside the .war archive.
If I place the content in any other location the filter cannot be set to operate on it.
If I place the content in the .war archive then every time a designer changes the content I have to rebuild and re-deploy the web-module.
Any idea how I can either have content (which is not in a web-module) be accessed through a filter , or how I can have content appear in a web-module from some other location?
Please help, this is a real show-stopper for our project. Thanks.

I don't think filters are really the way to go about this, rather, create a servlet that handles requests something along these lines:
void service(HTTPServletRequest request, HTTPServletResponse response) {
// get document root, base directory for all the xml files
String docRoot = request.getServletConfig().getParameter("docroot");
// get the document name
String path = request.getPathInfo();
// do some checking on path to make sure it doesn't contain
// '..' or anything like that, throw an exception if it does.
// create a java.io.File object representing the file:
File file = new File(docRoot, path);
if (/*browser is IE6*/) {
    // open the file (using FileInputStream) and copy it to
    // request.getOutputStream()
else {
    // pass the file through an xslt transformation that outputs
    // to request.getOutputStream()
}If this servlet is bound to a context called "context1", and the servlet is bound to "xml", requests for eg. /context1/xml/dira/dirb/doc1.xml will result in request.getPathInfo() returning "/dira/dirb/doc1.xml", given that the servlet-mapping element in web.xml is specified correctly (use a wild card: /xml/*).
And be warned, I just typed this in without trying to compile it, so it probably contains bugs!

Lightroom web module

Re "Lightroom Web Module"
In the "site info" panel, I type the word "exit"
In the "web or mail link" section, I copy and paste the web page address of the page on my site
I wish it to be directed to.
I preview this with the Lightroom "Preview in Browser" button.
All works perfectly well including the exit link.
I then export it into my website "local file".
Create a link from text on my web page to the lightroom created gallery (I'm using Dreamweaver)
Then save changes in Dreamweaver and click preview in browser.
The Gallery works fine with the exception of the exit link.
I have the same problem in the Web HTML Gallery
I have also downloaded Lightroom 3.6 from Adobe labs and had the same result.
Any Suggestions
Many thanks...David

Hi Pete. Thanks for your reply.
Tried replacing exit with home without any results
Doubbled checked the link address was correct in lightroom...it was.
Just tried something I had not tried before. Up untill now, I was using only the "preview in browser" in
Dreamweaver.
When I uploaded the gallery to the remote server and went to see if it worked on my site it did !!!!
Not sure why it won't work in the "preview in browser" in dreamweaver but.....a question for bigger brains than mine..
Many Thanks for your help
Dave

Web module problems in LR3

Similar Messages

Maybe you are looking for