Apache Url rewrite for portal URLs

Hi,
I have a requirement where i need to write simple URL's for the default portal uRL's
for example
inspite of using default url like "http://myserver:port/portal/server.pt/community/abc_xyz/123/efg_jkl/12345",
if user uses
"http://myserver:port/portal/server.pt/xyz"
It should navigate to same default URL.
Can somebody let me know how this can be achieved.
I know Url rewriting is done through Apache Url rewrites but do not have an idea how apache does it with portal Url's. What configurations need to be done in order to manage portal Url's with apache rewrites.
Thanks
Ajay

Hi Ryan,
Thanks for the reply. The link shows how to write the Rewrite rules in apache. I am familier with that. The actual problem is that how can the portal Url's be controlled by apache rewrites. My apache and weblogic are both on the same server instance but after writing the rewrite in httpd.conf file. It does not work out. Just want to know how can i tell apache to handle my portal Url's too.
Is there any specific entry that we need to make for doing this.
Thanks
Ajay

Similar Messages

Apache log analysis for portal page visits etc

We are about to go into production with Oracle Portal (9iAS rel 9.0.2.0.1).
I have been looking into how to gather statistics on web site usage and have concluded that I cannot get the information from within portal logs since many pages are served from the cache and there is no interaction with the database at all.
I think I need to, therefore, analyse the apache log files. Can anyone recommend a good 3rd party product for log analysis? I am also concerned that the portal specific urls might severely limit the usefullness of the data I can extract.
Has anyone used a log analysis tool in conjunction with Portal or knows of a product with a specific add-on for Oracle Portal (I have seen these for other portals and CMS products).
Any pointers appreciated, I am completely new to this area.
Peter.

Peter,
You might want to look at the "ClickStream Collector" that is included in a 9iAS installation.
I'm not sure if it will do what you want with Portal, but it's starting point.
Good luck!
Bill G...

Apache URL rewrite

Hi,
To make iPlanet work with apache, documentation ask me to change
httpd.conf so that all request comes into apache will forward to
iPlanet.
But I need to use URL rewrite module of apache contains the rewrite rule
RewriteRule ^/lmp
/NASApp/delivery/servlet/delivery;jsessionid=%{QUERY_STRING} [PT,NS]
which means if URL contains /lmp then rewrite to iPlanet handler
/NASApp/...etc
any one had successfully configure apache mod_rewrite works with
iPlanet?
In my pervious experience with Tomcat apache. I realize I have to load
the web-server-plugin module before module rewrite module. But if I do
that with iAS. then i get 404 not found on request to servlet.
thanks

We use iPlanet and apache with mode_rewrite
Try this:
RewriteEngine On
RewriteLog /usr/local/apache/logs/rewrite.log
RewriteLogLevel 1
# Rewrite Rules for App1
RewriteCond %{HTTP_HOST} ^app1.company.de$
RewriteRule ^/ https://myiWS.company.de:8011/NASApp/app1/mystartup.jsp

LSO -- where in configuration do you enter URL for portal / corses

LSO -- where in configuration do you enter URL for portal / corses

Hi Matt,
Another address not mentioned in the other posts is the CMS address where your courses are physically stored. In the IMG you will find it here:
Training & Event Management - SAP Learning Solution - Learning Portal - Content Player - Specify CMS Address
Enter the appropriate http: address beside the setting CPCFG/RSURL
Once a learner clicks to launch a course from the portal, the system will go find the appropriate course in the CMS directory and then find the Content Plyer address previously mentioned to launch the course.
Hope this helps.
Best regards,
Danielle

Two urls for portal

Hi,
1.Can anybody tell me how to configure two urls for portal?
2. How can I configure SSL certificates for both the urls?
our main aim is to have 2 urls one with Kerberos and one with non kerberos. want to define two urls for these two and want to install SSL certificates. Please help me.
Thanks
karunakar.M

Hi,
Blog: Using certificates with the SAP NetWeaver Portal
SAP Help: http://help.sap.com/saphelp_nw70/helpdata/en/65/6a563cef658a06e10000000a11405a/content.htm
Microsoft: http://support.microsoft.com/kb/931351
br,
Tobias

URL for Portal

Hi All,
Is it possible to find out the link/URL of the portal applications (for example UME or GRC) from the ABAP system. We have a test system but need to know the URL. Please help
Thanks
Vijaya

Vijaya,
The URL for portal on ABAP+JAVA system follows the convention
http://<hostname>:5<xx>00/irj/portal ---> This links to portal
http://<hostname>:5<xx>00 -
> This links to default Page of java
On the default page you will get options to go to UME and other options.
Regards,
Sandeep Nayak

Apache Directory Server as data source for Portal UME?

Hi,
Has anyone tried using Apache Directory Server as a Data Source for Portal UME? We would like to try that out. If anyone has tried before I would like to get the data source configuration file. ALso would like to know more in detail about the positives and negatives.
Thanks for your help.
Regards,
Vishnupriya

try to configure as stated in the following document.
http://help.sap.com/saphelp_nw04/helpdata/en/18/5cea2296190e4cb7faf9468ad793ea/content.htm
I have seen several discussions on sdn on the same, also make a keyward search on sdn.
Also check this for pros and cons for having Apache ...
Problem while configuring the Apache Web Server as the Intermediary Server
Edited by: SJ on Aug 3, 2008 10:11 AM

Apache installation for reverse proxy in linux for portal

dear all,
can u please guide me where to download the openssl apache foe linux for the reverse proxy
regards
revanth

Google is your friend...
It will take 15 seconds !
Regards,
Olivier

Setting apache reverse proxy for EP6SP2

Hi friends,
I want to set apache reverse proxy for EP6SP2. But after doing the following changes, it is showing the SAP J2EE Engine documentation page.
The following changes has been dont to httpd.conf:
NameVirtualHost 1.1.1.1:80
<VirtualHost 1.1.1.1:80>
ProxyRequests Off
ServerName ep6.xyz.com
ProxyPreserveHost On
proxyPass / http://ep6.xyz.com:50000/
proxyPassReverse / http://ep6.xyz.com:50000/
ErrorLog logs/base.80.error.log
CustomLog logs/base.80.custom.log common
</VirtualHost>
Help needed.
Regards,
Nilz

Hi,
I have a problem with my proxy:
ssl.conf.in like
ProxyPass /irj http://debmsu06.server.###.de:50300/irj
ProxyPassReverse /irj http://debmsu06.server.###.de:50300/irj
RewriteRule ^/$ /irj/portal [R]
If I use URL:
https://bebuyer.###.de/ goto https://bebuyer.###.de/irj/portal
but if I use
https://bebuyer.###.de/irj/
I get the info:
https://bebuyer.###.de/irj/HTTPS:/bebuyer.###.de:443/irj/index.html
What is happened? How I can redirect to /irj/portal?
Of course I can use
http://debmsu06.server.###.de:50300/irj/
Could you please give me some tips?
Best Thanks!
Heren Zhou

Need info to configure SSL for Portal Server in EP6SP2

Hello,
We need to configure SSL for Portal Server. We are using J2EE 6.20 Patch 25 and EP6SP2P4. The ITS is already using https and it creats lots of Session issues since Portal is not in https.
Is there any OSS Note or How to guide to configure Portal to use SSL.
Thanks.
- PK

Hi Marcel,
Thanx for your Post, I have a Question, we will use CISCO for load balancing and SSL termination but I have a big issue, the URL in the portal applciation is always the same ant the URL in the borwser, I guess al the other URL´s are in the Frames, how will we configure the SSL termination for the login page in example if the URL in the Browser appears always the same?
Thanx in Advanced!!!

How to create a new solution for portals?

Hi all,
In order to makde goinglive sesions for portals, I´ve updated SAP Solution Manager (SSM) to 7.0 EHP1-SP19.
Portals have two servers:
- Win 2003 for main application (NETWEAVER 7.0 2004s)
- HPUX 11.23 for database (Oracle 10.2.0.2.0)
I haven´t worked with solution manager until this update, and of course, I haven´t configured before.
I´ve a mix of terms, possible configurations:
- run SOLMAN_SETUP transaction after update ¿?
- install SMD ¿?
- install/configure SLD (we haven´t configured) ¿?
- create new solution, system components, logical components,...
I´ve tried to create a server, database, system, but I don´t know what is the right procedure.
I´ve seen that there is a transaction called "SOLMAN_SETUP" that I suppose I´ve have to run to configure the new version, but the EWAs configured before de update, runs properly.
Do you know the steps as more detailed as possbible to create the new solution for portals after update?
Does any of this steps/procedure impact into our configured and running EWAs and Goinglive sesions?
Thanks in advance.
Best Regards
Chema
Edited by: tsunix on Mar 29, 2010 9:26 AM

Hello,
Are you trying to get the EWA working for Go-Live check or Solution Manager? Based on my understanding you are trying to get your Solution Manager setup to be able to generate these reports. However, I will provide notes for both incase I am misunderstanding you.
Please review the following notes for getting your system prepared for Go Live checks:
207223    SAP EarlyWatch Alert processed at SAP
1095227 FAQ: SAP Hosting - Early Watch Alerts
207223    SAP EarlyWatch Alert processed at SAP
Also, you can visit http://service.sap.com/earlywatch for more help/documentation on this.
If you are trying to setup your EarlyWatch on your Solution Manager system, then please visit the following URL:
http://service.sap.com/ewa
You may also want to visit this note to see if it helps.
1257308   FAQ: Using EarlyWatch Alert
Thanks,
Mark

Using web dispatcher for portal and BW access

We currently have SAP's Web Dispatcher installed in our DMZ, which links the outside world to our internal enterprise portal installation. This configuration works fine for portal connectivity (see sapwebdisp.pfl below). However, we have BW reports (BW report iViews and URL iViews) which are accessed via the portal.
I do not know what configuration (if any) needs to additionally be set up on the Web Dispatcher host to allow connectivity. Currently, when accessing a BW report via the portal (coming from the Web Dispatcher) the report request is immediately terminated with an error due to a DNS lookup error (as the BW server is on our internal segment).
The Web Dispatcher is aware of both the internal portal server and BW server IP address and hostname and has the appropriate access (port/firewall) to retrieve these reports. Further, the HTTPURLLOC table is maintained (see example below) on the BW server as recommended in SAP Note 750292 (help file = http://help.sap.com/saphelp_nw04s/helpdata/en/59/31ae42e0fac911e10000000a1550b0/frameset.htm)
However, I can't get BW reports to work remotely. Should Is there something else that should be added to the Web Dispatcher's configuration? Is there something that I should be doing on the iView side (ie. not hardcoding hostname / port to the query string?). Please advise. Thanks!
sapwebdisp.pfl
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 0
Accessibility of Message Servers
rdisp/mshost = epprd1
ms/http_port = 8101
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
wdisp/add_clientprotocol_header = 1
wdisp/shm_attach_mode = 6
configuration for default scenario (medium size)
icm/max_conn      = 500
icm/max_sockets   = 1024
icm/req_queue_len = 500
icm/min_threads   = 10
icm/max_threads   = 50
mpi/total_size_MB = 80
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=80
icm/server_port_1 = PROT=ROUTER,PORT=443
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin
HTTPURLLOC table (BW):
MANDT
SORT_KEY
PROTOCOL
APPLICATN
FOR_DOMAIN
HOST
PORT
100
10
HTTPS
/SAP/BW/BEX
Internal_host.company.COM
8443
100
20
HTTPS
/SAP/BW/BEX
webdispatcher_host.company.COM
443

Hi James -
We're running EP 6.0 SP16 (WebAS 640 NW04) and BW 3.1/3.2 Content (WebAS 620).

(OT) Incompatible Apache Mod-Rewrite Rules

The following Apache mod-rewrite rule works:
RewriteRule ^About/([a-zA-Z0-9_/-]+)/?$
About/index.php?bout=$1 [L]
It displays URL's like mysite/About/Webmaster and
mysite/About/Search.
I've finally figured out how to apply a mod-rewrite rule to
my site's
home page...
RewriteRule ^/?([-a-zA-Z0-9_/]+)/?$ /index.php?home=$1 [L]
It displays URL's like mysite/Arizona and mysite/Africa.
But when I combine them...
RewriteRule ^/?([-a-zA-Z0-9_/]+)/?$ /index.php?home=$1 [L]
RewriteRule ^About/([a-zA-Z0-9_/-]+)/?$
About/index.php?bout=$1 [L]
The first rewrite rule appears to knock the second rule out
of action.
Does anyone know how to modify either rewrite rule to make
them compatible?
Thanks.

On 4/26/06 8:52 AM, "David Blomstrom" wrote:
> The following Apache mod-rewrite rule works:
>
> RewriteRule ^About/([a-zA-Z0-9_/-]+)/?$
About/index.php?bout=$1 [L]
>
> It displays URL's like mysite/About/Webmaster and
mysite/About/Search.
>
> I've finally figured out how to apply a mod-rewrite rule
to my site's
> home page...
>
> RewriteRule ^/?([-a-zA-Z0-9_/]+)/?$ /index.php?home=$1
[L]
>
> It displays URL's like mysite/Arizona and mysite/Africa.
>
> But when I combine them...
>
> RewriteRule ^/?([-a-zA-Z0-9_/]+)/?$ /index.php?home=$1
[L]
> RewriteRule ^About/([a-zA-Z0-9_/-]+)/?$
About/index.php?bout=$1 [L]
>
> The first rewrite rule appears to knock the second rule
out of action.
> Does anyone know how to modify either rewrite rule to
make them compatible?
>
> Thanks.
I'm not an expert on mod_rewrite, but you might be able to
get what you want
simply by reversing the order of the rules:
RewriteRule ^About/([a-zA-Z0-9_/-]+)/?$
About/index.php?bout=$1 [L]
RewriteRule ^/?([-a-zA-Z0-9_/]+)/?$ /index.php?home=$1 [L]
In theory, that should redirect your /About pages, and the
[L] tells Apache
not to parse any more rewrite rules, so the first rule (which
looks like it
simply redirects *everything*) wouldn't come into play.
There's something about times when Apache still parses
rewrite rules even
after the [L] flag, though, so that might not work. Why don't
you see if
that works, and if it doesn't, we can look at it further.
Sonjay

Help, need to change IP address on host database for Portal

Hi folks,
Rather urgent assistance (as usual) needed. I have an installation working correctly on a pair of Win2k machines, one as the 9i database, one as the 9iAS/Portal. The app server has 2 NIC cards, one with public IP address (which is ok), one on the LAN. I need to reconfigure the LAN addresses on both the machines. Initial Portal install done without DNS, i.e. actual server/host addresses entered in the configuration.
I have tried changing all of the TNS/Listner settings and the NIC card IP addresses and restarting the machines. The likes of SQLPlus work ok, with the TNS connect name allowing over the LAN access into the database with the new LAN addresses. I cannot seem to get the 9iAS/Portal to find the repository with the new addresses.
Can someone help please? I can't find the answer in any documentation or other postings.
Thanks in advance
Rob

There are other modes of operation for the plasst as well. I am listing them below but the formatting will make it difficult to read. If you like I can email it to you.
Bill G...
Configuring Portal when the HTTP server host name of the Infrastructure is changed
Run the following from the $ORACLE_HOME/assistants/opca dir
ptlasst.bat -mode SSOPARTNERCONFIG -i typical -sdad portal -host myApache.domain.com -port 7777 -silent -verbose
NOTE:
(1) This command would create a new Portal partner application in the SSO to reflect the changes of the Infrastructure. Before running this command please ensure to configure the SSO with the correct hostname by running the ssocfg.bat script located in the Infrastructure install (<infra_home>\sso\bin).
The value for -host parameter will be the IP address of the infrastructure server and -port will be the port where the infrastructure http server is running on.
Configuring Portal when the HTTP server host name of the Middle tier is changed
ptlasst.bat -mode MIDTIER -i typical -host myApache.domain.com -port 7777 -ldap_h myOID.domain.com -ldap_p 389 -ldap_w welcome -pwd secret123 -portal_only -oh /home/oracle -chost myHostname.domain.com -cport_i 8001 -cport_a 8000 -wc_i_pwd invalidator -mc false -mi true -silent -verbose
NOTE :
(1) The -host value should match the serverName value of the httpd.conf
(2) The -chost should be updated with the correct webcache hostname. In a default iAS midtier install the -host is same as the -chost.
The value for -host parameter will be the IP address of the midtier(portal) server and -port will be the port where the portal is running on.
Parameter Description Default Value Mandatory
-i install_type Installation Type
In the typical mode, the OPCA would get the Infrastructure information like the Portal schema name, Portal schema password, connect string to the Portal repository, SSO Partner application schema and password, SSO Password store schema and password and connect string to the SSO repository from the Repository Access API's.
In the custom mode, the OPCA would take whatever is passed as the command line arguments.
CUSTOM
-mode mode The different install modes are : PORTAL, SSO, SSOPARTNERCONFIG, LANGUAGE, MIDTIER, ALL, SYSOBJECTS , DEINSTALL
-s portal_schema Oracle Database schema for Portal database objects. In an iAS 9.0.2 install
the default Portal schema name is portal portal
-sp portal_password Password for Portal schema. In an iAS 9.0.2 install the portal schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for details. <portal_schema>
-c portal_connect Connect string to connect to the Portal repository <hostname>:<port>:<sid>
-p sys_password The Oracle Database password for the Oracle SYS user MANDATORY
-sdad portal_dad DAD for the Portal schema. Create the DAD to the Portal repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <portal_schema>
-host portal_host Hostname of the HTTP server for Portal. This should match byte to byte with whatever is present in the ServerName attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier. MANDATORY
-port portal_port Port of the HTTP server for Portal. The Port attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier would provide the value. 7777
-ldap_h oid_host_name Host name of the OID server MANDATORY
-ldap_p oid_port_number Port number of the OID server 389
-ldap_d oid_admin_DN Admininstration DN cn=orcladmin
-ldap_w oid_admin_pw Password for DN welcome
-pwd initial_password Initial Password for seeded OID users. In iAS 9.0.2 install this is defaulted to the iAS instance password of the midtier installation. MANDATORY (for ALL or MIDTIER)
-das_public Add Portal Groups to DAS Public Groups. The values could be Y or N. The default is Y. The setting publishes the Portal groups that the user can add to when creating the new user in OID. Y
-u default_tablespace Install Portal objects in this tablespace. The default tablespace selected should have atleast 75 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The default tablespace selected by default is users tablespace. users
-t temporary_tablespace Use this tablespace for temporary objects. The temporary tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The temporary tablespace selected by default is temp tablespace. temp
-d document_tablespace Install Portal document table in this tablespace. The document tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note
"What are the recommended tablespace size required for Portal installation ?" for details. The documented tablespace selected by default is users tablespace. <default_tablespace>
-l logging_tablespace Install Portal logging tables in this tablespace. The Logging tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Logging tablespace selected by default is users tablespace. <default_tablespace>
-in index_tablespace Install Portal index in this tablespace. The Index tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Index tablespace selected by default is users tablespace. <default_tablespace>
-lang language Abbreviation for the language to install us
-m language_mode Specifies the mode for language installation
if sso, translations only for Login server.
if portal, translations only for Portal.
if -m not specified, translations are installed for Both
-demo Install Portal webview demos
-silent Run mode for Portal Configuration Assistant. There is no UI provided by OPCA in the iAS 9.0.2 install. Use -silent option always
-verbose Log mode for Portal Configuration Assistant. If this parameter is not set, logging information would be in brief and the OPCA would abort the install if it encounters any errors of kind
ORA-, PLS- or SP2 errors.
-report Install reports integration with Portal
-owa Install OWA packages along with Portal This option behaves the same as the SYSOBJECTS mode.
-sso_only Configure only SSO in mid-tier mode
-portal_only Configure only Portal in mid-tier mode
-available Language will be available for user translation
-chost cache_host Cache host for Web Cache <hostname>
-cport_i cache_inv_port Cahe port for Web Cache Invalidation 1100
-cport_a cache_adm_port Cahe port for Web Cache Administration 1000
-wc_i_pwd wc_inv_passwd Web Cache invalidator password invalidator
-wc wc_on_off_flag Web Cache ON/OFF flag to enable or disable WC. The default is ON. If set to OFF Portal would not use Webcache though Web Cache may be up and running. on
-o sso_schema Oracle Database schema for Login Server objects. In an iAS 9.0.2 install the default SSO schema name is orasso orasso
-op sso_password Password for Login Server Schema. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso. MANDATORY for the following modes:
-MIDTIER: except when '-portal_only' is specified
-LANGUAGE: except when '-m portal' is specified
-DEINSTALL: except when '-drop PORTAL' is specified
-odad sso_dad DAD for Login Server objects. Create the DAD to the SSO repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <sso_schema>
-sso_c sso_connect Connect string to connect to the SSO repository If the Portal and SSO use the same database this option need not be passed and would default to the -c argument. <hostname>:<port>:<sid>
-sso_h sso_host Hostname of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP server used for the Portal.
-sso_p sso_port Port of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP port used for the Portal.
-pa papp_schema SSO Partner Application Registration Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_pa <sso_schema>_PA
-pap papp_password SSO PA Schema Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_pa <papp_schema>
-ps pstore_schema Password Store Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_ps <sso_schema>_PS
-pp pstore_password Password Store Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_ps. <ptore_schema>
-pd pstore_dblink Database link from Portal schema to Password store. If the Portal and SSO use the same database this option need not be passed. <portal_schema>_DBLINK
-p_tns pstore_tns TNS connect string to Password Store. If the Portal and SSO use the same database this option need not be passed. The tnsalias should be created in the iAS 9.0.2 Portal middle tier.
-s_tns portal_tns TNS connect string to Portal
-ssotype ssotype SSO install type. Valid values are repository, midtier, all Repository
-ultrasearch Ultrasearch configuration
-drop drop_obj Drops either PORTAL or SSO or ALL (Both)
if PORTAL, drops Portal schema and OID entries.
if SSO,drops Portal schema and OID entries.
if ALL, drops Portal and SSO schema and OID entries
-oh oracle_home Oracle Home
-mi midtier_install Midtier Installation
-mc midtier_config Midtier Configuration
-ssl Use SSL protocol for configuration. Pass this parameter only if SSL configuration is required. If this parameter is passed the -port passed should also be the SSL port of the HTTP server. Bt default this is not passed.
-emhost em_host Enterprise Manager host for monitoring <hostname>
-emport em_port Enterprise Manager port for monitoring 1810
-iasname ias_name Name of the iAS instance that the install is installing on

Setting up the Apache HTTP Plugin for several BEA Servers

Hey together,
i would like to setup the apache http plugin for several bea-servers.
I am running apache 1.x on my hp-ux system. There are 2 bea-server-domains on this box and both should be proxied by the plugin simultaneously.
As far as i know it isn't possible to run 2 or more instances of the apache webserver. I heard of virtualhosts, maybe i should try this one out.
Somebody knows how to deal with this problem or does any1 know if virtualhosts could cope with my needs?
Thanks in advance

Ok here i am again and i'm stuck. Here my wishes again:
there are 2 weblogic-instances (domains) running on a machine xxx, instance A listening on port 8041, instance B listening on port 8051. I want to configure apache virtualhosts in combination with weblogic plugins, so that request with /ld will be sent to instance A while requests with /ldd will be sent to instance B. Both are no clusters. Therefore i tried it with the following configuration (httpd.conf):
<VirtualHost xxx:8080>
     DocumentRoot "/opt/hpws/apache/htdocs"
     ServerName xxx:8080
     <IfModule mod_weblogic.c>
     WebLogicHost xxx
     WebLogicPort 8041
     #MatchExpression *
     #PathPrepend=/test2
     </IfModule>
     <Location /ld>
     SetHandler weblogic-handler
     PathTrim /ld
     </Location>
</VirtualHost>
# VirtualHost2 = xxx:8090
<VirtualHost xxx:8090>
     DocumentRoot "/opt/hpws/apache/htdocs"
     ServerName xxx:8090
     <IfModule mod_weblogic.c>
     WebLogicHost xxx
     WebLogicPort 8051
     #MatchExpression *
     #PathPrepend=/test2
     </IfModule>
     <Location /ldd>
     SetHandler weblogic-handler
     PathTrim /ldd
     </Location>
Doesnt really work. Can some1 help please?
Thanks

Apache Url rewrite for portal URLs

Similar Messages

Maybe you are looking for