Unable to forward requests from webserver

I am trying to set-up iWS 6.0sp4 to forward requests to the application server but I always get not found as the webserver is just looking at its own document root. I have deployed the fortune ear (from 6.5) and can access that via the application servers own http server perfectly well. I have added the plugin package to the webserver and added the following into the magnus.conf
Init fn="load-modules" shlib="<install_dir>/lib/webserver-plugin/solaris/iws/libpassthrough.so" funcs="init-passthrough,auth-passthrough,check-passthrough,service-passthrough" NativeThread="no"
Init fn="init-passthrough"
and to the obj.conf
NameTrans fn="assign-name" from="(fortune/fortune/*)" name="passthrough"
NameTrans fn="assign-name" from="(fortune/*)" name="passthrough"
ObjectType fn="force-type" type="magnus-internal/passthrough"
Service type="magnus-internal/passthrough" fn="service-passthrough" servers="http://<application server http listener>"
Error reason="Bad Gateway" fn="send-error" uri="$docroot/badgateway.html"
</Object>
The webserver starts up without any errors but never forwards any requests what might I be doing wrong?

I followed the instructions found in the App Server 7 documentation and everything worked fine.
The instructions I followed are in the document found at this link:
http://docs.sun.com/source/816-7156-10/agplugin.html#17655
Just FYI...
I also checked with Sun about why this process is now necessary and I asked about what happened to the web connector from 6.x. Sun had this reply:
The Web Server Plug-in is the new web connector. It just hasn't been wrapped with an installation yet ... which is why it is tedious. The old Plug-in for 6.5 would ultimately have the same type of obj.conf entries. I'm not sure if there will be an installation wrapper for it once the Enterprise Edition is released.
The Web Server Plug-in is different right now in that it doesn't 'know' about multiple instances yet. These are capabilities that will be introduced in the Enterprise Edition in March. Of course, that doesn't stop you from having multiple instances of the web server talking to multiple instances of the app server. It just means that the web server instances have to be directed to the app server instances rather than discovering them.

Similar Messages

Trouble forwarding request from a servlet to a JSP in OAS 4.0.8.1 on NT

The OJSP release notes state that:
"Servlets and JSP cannot coexist as the same application" and "Requests cannot be passed between two separate applications."
Does this mean that my attempts to use the
the servlet RequestDispatcher to forward a request to a JSP are futile? If so, is this a problem that will be fixed in the future? I would like to use this feature!
This is the code (based on a sample from Sun's JSWDK 1.0.1) that doesn't work:
servletToJsp.java
import javax.servlet.*;
import javax.servlet.http.*;
public class servletToJsp extends HttpServlet {
public void doGet (HttpServletRequest request,
HttpServletResponse response) {
try {
getServletConfig().getServletContext().getRequestDispatcher("/jsp/jsptoserv/hello.jsp").forward(request, response);
} catch (Exception ex) {
ex.printStackTrace ();
I am able to use the <jsp:forward page="/servlets/servletToJsp" /> directive to go from a JSP page to a servlet (across two OAS Applications) and I also can forward a request via the dispatcher from one servlet to another in the same OAS application.
Any help in this area would be appreciated. Thanks.

I'm using OAS 4.0.8.1
You mean servlet to JSP does not work and JSP to servlet works for you????Yes - but I've only tried very simply examples.
That's different from my understanding. If you are using OAS 4081, both cases should not work.
The problem you mentioned will be fixed in future release of OAS.That's good to know - thanks!
null

Webdispatcher to forward requests from internet to intranet?

We need to direct requests from internet to our content server which is in the intranet (so that the content server images can be seen from the internet).
We have a WAS WebDispatcher in the DMZ. Can we use this WD to provide the connectivity?
For example:
Our content server intranet URL is:
http://contenterv.com:1090/path/image.jpg
Our WebDispatcher URL is:
http://webdisp.com/app_name
http://webdisp.com/app_name should resolve to http://contenterv.com:1090/path/image.jpg
We tried WD http forwarding but it just forwards the request, does not resolve the name transparently. So the forwarding works but since http://contenterv.com:1090/path/image.jpg is not known in the internet, it fails.
Thanks

>
Ghochi Elin Kuswoyo wrote:
> hi guys,
>
> you need to add parameter in your sapwebdisp.pfl (sap webdispatcher profile) :
>
> icm/HTTP/redirect_0 = PREFIX=/,TO=/path_image
>
> thanks
No, this wont work, becuase you need reverse-proxy function rather than URL redirection, because internet user wont be access the intranet server even you give them the URL.
I cannot get you the detailed confguration, but you can refer to web dispatcher cascade configuration. play with the following parameters:
wdisp/server_info_location
wdisp/group_info_location
wdisp/url_map_location
>
Cons wrote:
> So in short, get your networking guys to do this, SAP cannot help in any way.
it's not ture, web dispatcher can be used reverse proxy, of course you also can use other solution like Apache. However it's not recommened to use NAT, which might breach your network security.
Cheers,
Denny
Edited by: Denny Liao on Jan 28, 2010 11:26 PM

How to configure bea apache plugin to forward request from apache to bea se

Hi,
I have an apache server and a bea weblogic application server. For security reasons, I wold like to configure a bea plugin on the apache server to redirect the client http/https requests from the apache2 server to bea application server.
I have gone through the bea documentation and configure my apache2 httpd.conf as follows
LoadModule weblogic_module modules/mod_wl_20.so
<IfModule mod_weblogic.c>
WebLogicHost myweblogic.server.com
WebLogicPort 7001
MatchExpression *.jsp
</IfModule>
<Location /weblogic>
WebLogicHost myweblogic.server.com
WebLogicPort 7001
SetHandler weblogic-handler
PathTrim /weblogic
</Location>
Then Restarted the apache2 and tryied to acces bea application through http://myweblogic.server.com/weblogic/
and http://myweblogic.server.com/something.jsp
It did not work
httpd is started propery.
Any help would be highly apreciated
Many Thanks
Ushas Symon

I have no experience with nginx and varnish and asking configuration problems regarding these products is perhaps beyond the scope of this forum.
While configuring varnish, we are getting issues and unable to connect server from my browser if I change port 80.
You did not describe the issues, but it is possible and very common that your IP Firewall is blocking access to ports other than 80 and 22. For testing, you can simply turn it off. If you do not know how, please post your OS distribution version first, as it all depends.

Unable to delete requests from ODS

Hi Experts,
I am trying to delete requests fwhich is having some added records rom an ODS. I changed the status of QM to RED and in the monitor screen as well. Now, when I try to select the request and delete, a trash can appears and after hitting the refresh button the reportinng availability appears against the request.
I deleted the entries in the change log table...then I was able to delete the request from the ODS. Now when I try to reconstruct those deleted requests from the Reconstruct tab by changing the QM status in the monitor to green, the status of these request are in Yellow and there are updated records but the added records are 0. When I try to change the QM status it give s message "Request is already (partially) activated, no further QM action is possible.
How do I change the request QM status to Green and the get all the added records as there were in previous instead of 0's with out reloading the ods from r/3.
Thanks in advance,
HT

Hello,
This error may be RSMPC141 error.
Please see Note 643880 and Note 849857
this may occur becos of loss f records in change log.
You will need to reload to fix this problem
regards,
karthik

Unable to delete request from ODS - BW 3.5

Hi experts,
I am not able to delete request from ODS in BW 3.5, patch level 21. I put the request red, but it does not help to delete it. The request is full load and quite hudge (16GB). Deleting actually takes too long (several hours), but does not finish, so I cannot tell you any error description. It seems that this job can run forever... I was trying to activate the request before, but because of a tablespace limitations I received some short dumps. That is why I am trying to load it agin in smaller parts. It is strange thou that in Manage/requests tab the request has flag 'available for reporting' but the data cannot be viewed as active (only as new data). Any ideas, OSS notes?
Thank you,
Michal

Hi,
If you want to delete requests manually from the ODS tables.
1. tcode se16.
2. delete the request in these tables : RSICCONT (delete activated requests OR
Make the selective deletion of the contents of that request), RSMONICDP, RSODSACTREQ (give the name of the ODS and the
request ID and delete all the entries pertaining to this selection in that table.), RSODSACTUPDTYPE.
You can check OSS Notes 947481
Regards.

Unable to delete request from write-optimized DSO (Error during rollback)

Hi Gurus,
I am trying to delete a delta request from a Write-Optimized DSO. This request was uploaded with a DTP from another Write-optimized DSO.
The actual overall status of the request is RED and the description of that status is now: 'Error during rollback of request DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR; only rollback allowed'.
I checked the log of all Request Operations in DataStore (from the same line where the red request is now) and I see my several attemps to delete this request under a RED radiobutton with the title Rollback. The details for this error are the following:
Could not delete request data from active table
Message no. RSODSO_ROLLBACK114
Diagnosis
The system could not delete the request data from the active table of a write-optimized DataStore object.
System Response
Write-optimized DataStore object: DTFISO02
Active table: /BIC/ADTFISO0200
Request: DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR
Procedure
Search for Notes containing the key words "Delete write-optimized DSO PSA"
I am relatively new to SAP BI 7.0 and I do not know how to delete this request. Any help will be highly appreciated !!
Leticia

Hi Leticia:
Take a look at the SAP Notes below.
Note 1111065 - "701: Delta consistency check for write-optimized DSOs"
Note 1263877 - "70SP20: Delta consistency check for write-optimized DSOs"
Note 1125025 - "P17:PSA:DSO:ODSR missing in PSA process for write-opt. DSO"
Additionally, some ideas from the alternative presented on the blog by KMR might help you.
"How to generate a selective deletion program for info provider"
Regards,
Francisco Mílán.

How to send request from webserver to application server

Hi All,
I have below setup :-
A)) Apache http server running over 192.168.206.128:8080
B)) Weblogic application server admin server running on 192.168.206.128:7001
-->i have a cluster with 2 managed servers
-->cluster address us 192.168.206.128:7003,192.168.206.128:7004
--> Also i have a Proxy Server running at 7011 port and have in memory sesion replication active through this.
C)) I have application MyWebApp deployed over the cluster and ProxyApp deployed over Proxy Server. Now i want to use webserver to request for those applications. Can somebody please help me the way to do that.
Regards
Sharad Jain

Hey Ravi,
After some reasearch and going through your posts, i am now able to atleast go to the first jsp page of the application.like thorugh the below link
http://192.168.206.128:8080/MyWebApp/First.jsp
But after reaching this page when i start navigating to get through a servlet then it says page is on available on this server. please help me what i need now..
i am also copying the httpd.conf file below:-
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do not begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/foo_log".
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "/usr/local/apache2"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
Listen 192.168.206.128:8080
Listen 8080
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available before they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User daemon
Group daemon
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/usr/local/apache2/htdocs"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/usr/local/apache2/htdocs">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "logs/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you do
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and not in this file.
CustomLog "logs/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target directory are treated as applications and
# run by the server when requested rather than as documents sent to the
# client. The same rules about trailing "/" apply to ScriptAlias
# directives as to Alias.
ScriptAlias /cgi-bin/ "/usr/local/apache2/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock logs/cgisock
</IfModule>
# "/usr/local/apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/usr/local/apache2/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
LoadModule weblogic_module modules/mod_wl_22.so
<IfModule mod_weblogic.c>
WebLogicCluster 192.168.206.128:7003,192.168.206.128:7004
MatchExpression *.jsp
MatchExpression *.xyz
</IfModule>
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
=====
waiting for the reply :-
Regards
Shartad Jain

Unable to forward requests across web applications

Hi,
please let me know if there is a solution to the following problem.
I have 2 EARs, each having a web application inside.
Whenever the user submits a request, it goes to a filter in webApp1. This filter checks the request.getRequestURI() and if a specific url pattern is present, it modifies the request using a wrapper and then dispatches it to webApp2. The code in the filter is as follows,
The original url is,
http://localhost:8001/ivx/odr/account/frameset.do
HttpServletRequestWrapper rw = new HttpServletRequestWrapper((HttpServletRequest)request)
public String getRequestURI()
     //Here I return "/odr/account/frameset.do"
public String getContextPath()
     //Here I return "/odr" which is the context path of webApp2
public StringBuffer getRequestURL()
     //Here I return "http://localhost:8001/odr/account/frameset.do"
public String getServletPath()
     //Here I return "/account/frameset.do"
Now the filter in webApp2 intercepts the request and after some security checks, does a chain.doFilter(). The struts RequestProcessor is called, which determines the mapping for "/account/frameset.do" and is able to create a valid ActionForward object. Finally when the request is forwarded from the requestProcessor, I get a "404-Page cannot be displayed" error.
Is this because,
1. The contextPath is getting lost somewhere ? (I checked the request, it has the context Path of webApp2 correctly)
2. The request itself is lost ?
3. The ActionForward object points to a JSP file location like "/account/frameset.jsp" ? (The jsp is located in the account folder directly below the webApp2 context root folder.)
Thanks.

I followed the instructions found in the App Server 7 documentation and everything worked fine.
The instructions I followed are in the document found at this link:
http://docs.sun.com/source/816-7156-10/agplugin.html#17655
Just FYI...
I also checked with Sun about why this process is now necessary and I asked about what happened to the web connector from 6.x. Sun had this reply:
The Web Server Plug-in is the new web connector. It just hasn't been wrapped with an installation yet ... which is why it is tedious. The old Plug-in for 6.5 would ultimately have the same type of obj.conf entries. I'm not sure if there will be an installation wrapper for it once the Enterprise Edition is released.
The Web Server Plug-in is different right now in that it doesn't 'know' about multiple instances yet. These are capabilities that will be introduced in the Enterprise Edition in March. Of course, that doesn't stop you from having multiple instances of the web server talking to multiple instances of the app server. It just means that the web server instances have to be directed to the app server instances rather than discovering them.

Forwarding request from JSP/Servlet to EJB

Is it possible to forward the HttpRequest,HttpResponse objects from a Servlet/JSP to an Entity/Session bean ?
ie To forward the call using RequestDispatcher/forward to a Session bean which in turn calls the entiy bean for updating DB
Ramesh

I don't think that's possible and even if it is there's an easier way. Normally you just create an instance of the session bean in a servlet and pass it the information. The session bean then calls the entity bean which updates the database. You don't have to forward the request - just pass the data to the bean.

Can't forward request from Apache to Tomcat on second instance

Hi,
I am trying to create 2 separate environments (dev and test) on one powerful
Unix server which has 2 network cards, 2 IP addresses, 2 server names...
Using Apache 2.0.43 and Tomcat 4.1.29/JBoss 3.0.7, mod_jk 2.0.43
on Solaris 9, Intranet environment.
Everything is fine on the first instance,
but on the second instance when I do http://server2,
Apache still can't redirect to second Tomcat/JBoss:
"Forbidden
You don't have permission to access / on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.48 (Unix) mod_jk2/2.0.2 Server at mopppgctxat1.pfizer.com Port 80"
If I do http://server2:8080, getting it all right.
I made all internal ports on the second instance different from the first:
e.g. 8080->8180, 8009->8109, etc.
Even tried to change "Listen <ip2>:80" to 81, same error.
Curiously, jk2.properties is totally commented out.
I haven't compiled mod_jk, just copied the binary from the 1st instance.
Can that be a problem ?
Any help is very appreciated.
Thank you,
Oleg.

By trying and trying I got it to work .... long hours
I removed the queue to queue option and the subscriber name from the subscriptions definition. And then I removed the destination-queue on the propagation schedule. Then it worked.
Mette

Unable to delete request from an ODS

Hai All,
I have a requestng in an ODS which I am trying to delete in the Manage ODS- screen by selecting the request and then deleting it. But every time I press delete, I get the trashcan symbol in place of the reporting symbol of the request and when I press refresh , the trash can disappers and the reporting Icon comes back. Any idea why this is happening? I then changed the QM status of both the request and in the Monitor and tried to delete without any luck.
Can somebody please tell me what the problem is, I have no errors showingup but the request is not getting deleted.
Thank you.

Hi Visu,
Check if you have set the status of the request you want to delete as RED before deleting it..
We had a similar issue bcoz of this before..
Also check if all the requests that came in after that are also deleted..
Ashish.
Message was edited by: Ashish Gour

Forwarding proxy requests from ports other than 80

Hi,
Is there a way to forward requests from ports other than 80 to the proxy address? For example, trying to define a rule to forward the requests from port 8080 to proxy_ip...
Best regards,
Emre

Hi Emre,
Have you looked into using ipfilter port redirecting ?
It may depend on your configuration.
/etc/ipf/ipf.conf
pass in quick from any to any port = 8080 keep state
pass out quick from any port = 8080 to any keep state
/etc/ipf/ipnat.conf
rdr <Interface> <hostname or IP> port 8080 -> <hostname or IP> port 8080 tcp
Edited by: Hodware on Mar 4, 2013 7:24 AM

Deleting the request from DTP of master data.

Hi,
I loaded data i attributes of 0costcenter. But the request was showing me yellow color. Its not been deleted. I deleted it from RSICCONT. But still while running DTP its showing me error as " Request 7.928 is already being processed".
Please tell me some solution as i cant delete the DTP.
Roma

hi
check the links
http://wiki.sdn.sap.com/wiki/display/BI/ChangeStatusofDTPRequest
Unable to delete request from DSO
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02ba9e7-bb6f-2c10-09b4-e86b9fcbad41?QuickLink=index&overridelayout=true
may help you

Exception while forwarding request to another jsp file.

Hi
I am getting following exception when I try to forward request from one jsp file to another using <jsp:forward> . I am using tomcat 5.5.9.
thanks in advance
org.apache.jasper.JasperException
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:370)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:66)
at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:81)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:293)
at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:693)
at org.apache.jasper.runtime.PageContextImpl.access$1000(PageContextImpl.java:65)
at org.apache.jasper.runtime.PageContextImpl$11.run(PageContextImpl.java:647)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:645)
at org.apache.jsp.mseries.SpareCheckSend_jsp._jspService(org.apache.jsp.mseries.SpareCheckSend_jsp:141)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:275)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:534)

I believe you will need to more clearly describe what you are trying to do and what the problem is that you are having before you get a reply to your question.

Unable to forward requests from webserver

Similar Messages

Maybe you are looking for