JMS setExceptionListener doesn't work in a j2ee container?
I have just upgraded to Oracle SOA suite 10.1.3.1.0 from Oracle BPEL 10.1.2.0.2
I have redeployed a servlet which I had running on my previous oc4j server.
However when my servlet now attempts to send a jms message to the server I get an exception raised:
QueueConnection[Oc4jJMS.Connection.ghc-pc029.5a62f421:10f2ebe2218:-8000.333]: cannot invoke method "setExceptionListener" within the J2EE container.
Please could you explain why the below method can not be invoked in a J2EE container.
javax.jms.QueueConnection#setExceptionListener(ExceptionListener listener)
(retrieved from com.evermind.server.rmi.RMIInitialContextFactory)
Is this a defect? regression? or limitation?
Thanks,
Peter
Peter,
Is this a defect? regression? or limitation?Creating exception listeners is explicitely prohibited by the J2EE 1.4 specs (see http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf, section 6.6, page 103).
We had to enforce this in 10.1.3.1 to be compliant and pass the Compatibility Test Suite (CTS). The idea is that all connection-related tasks are delegated to the container. WHile making things simpler, it also certainly removes some flexibility.
Hope this makes sense.
/Demed
Similar Messages
-
When I installed jms (j2ee1.3) my lookups doesn't work anymore...
Hi. I was using j2se 1.3 and performed some lookups on objects from an Oracle 8.1.7.
Then, in order to use jms, I installed j2ee 1.3 and j2se 1.3.1. Now my lookups doesn't work anymore, but my lookups on jms objects (por example Queue or QueueConnectionFactory) does work fine. This is the code that produces the error, and the error:
****** CODE *************
String serviceURL = "sess_iiop://desarrollo:2482:SCANALES";
String objectName = "/test/sInformacionSalida";
ServicioInformacionSalida sis = null;
Hashtable env = new Hashtable ();
env.put (Context.URL_PKG_PREFIXES, "oracle.aurora.jndi:com.sun.enterprise.naming");
env.put (Context.SECURITY_PRINCIPAL, "USER");
env.put (Context.SECURITY_CREDENTIALS, "USER");
env.put (Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
InitialContext ic = null;
try {
ic = new InitialContext(env);
} catch (NamingException nE) {}
System.out.println("ASIF: Lookup de servicio de salida de informacion de formateo...");
try {
sis = (ServicioInformacionSalida)ic.lookup(serviceURL + objectName);
} catch(NamingException nE) {
System.out.println("ASIF: Error en el lookup: " + nE.getExplanation());
System.out.println("ASIF: " + nE.toString());
nE.printStackTrace();
System.exit(-1);
**************** ERROR ******************
ASIF: Error en el lookup: Unknown service: 200.12.145.40:2482:SCANALES
ASIF: javax.naming.CommunicationException: Unknown service: 200.12.145.40:2482:SCANALES
javax.naming.CommunicationException: Unknown service: 200.12.145.40:2482:SCANALES
at oracle.aurora.jndi.sess_iiop.SessionCtx.initialContext(SessionCtx.java:647)
at oracle.aurora.jndi.sess_iiop.SessionCtx.<init>(SessionCtx.java:67)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.createSession(ServiceCtx.java:161)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.login(ServiceCtx.java:349)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.defaultSession(ServiceCtx.java:219)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.lookup(ServiceCtx.java:373)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:256)
at oracle.aurora.jndi.sess_iiop.sess_iiopURLContext.lookup(sess_iiopURLContext.java:242)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at SimpleQueueSender.main(SimpleQueueSender.java:152)**********************************************
Last, from the %J2EE_HOME%\lib\classes\jndi.properties:
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
java.naming.factory.url.pkgs=com.sun.enterprise.naming
The weird thing is that when I remove %J2EE_HOME%\lib\j2ee.jar from the classpath, the lookup works fine again but, of course, I can't use the jms classes.
From the "Unknown service" message, I presume that the problem is related to the service provider and/or something with the environment properties.
PLEASE ANY HELP!!
Thanks.This seems weird enough for bringing to the attention of the JNDI technical team.
If you have not already done so, you might want to send this message directly to them at [email protected]
There seems to be some incompatibility between Oracle classes and J2EE 1.3 classes. As you have pointed out, in some service provider classe(s). -
JMS Migration - doesn't seem to work properly
Hi,
I have a cluser with three managed nodes. I am experimenting with manual
migration of JMS services when the 'active' server goes down. The behaviour
it exhibits is distrinctly odd. If I kill the active server, and try to use
the console to migrate, then the various servers never seem to be able to
agree on what the current server is. server1 thinks its server1 (which it
is). Server2 and 3 seem to think it's server2. If I migrate from the (now
killed) active server to an active one, by navigating to
server1/control/Migrate, then I get the option to migrate from server1 to
server 2. If I confirm I want to do this, then it says migrating from
server1 to server1!!! WLS generally seems to get very confused as to which
is the current servers, and which servers can be the migration target. If I
start with a fresh cluster, with 3 managed nodes, and start up the admin
server and 2 of the managed nodes, then WLS (rather bizzarly) chooses the
third (not started) node as the one to associate the JMS services with! If
I try to use the command line utility (weblogic.Admin) to migrate instead of
using the console, then things get even worse. It will only correctly
peform the migration rarely. It often tells me that the target server that
I'm migrating to is already the active one (which it isn't). Even worse -
it often says 'OK' but in fact non of the servers are then hosting the JMS
service.
Anybody else experienced these sorts of migration issues. I've tried this
with WLS 7.0 SP1 and WLS 7.0 SP2, and WLS 8.1 SP1 and they all exhibit the
same behaviour.
Cheers,
Stanley.
After some testing I found out that when you migrate to server2 from server1, it
does the migration, server2 gets updated and knows that it is now hosting JMS
servers, however server1 does not get updated, this can be seen in the console
under migration check the console before and after the migration, server1 will
still show as it being the JMS host or target.
There are 2 ways to over come this.
1. Migrate from server1 to server2 and from server2 to server2, the second step
updates server1's properties and now the console shows up correctly.
2. Do not migrate just target JMS server to which ever server you want under the
targets tab under JMS server configuration. This seems to work using the console.
Anil
"Stanley Beamish" <[email protected]> wrote:
>Hi,
>
>I've attached the info as you requested. config_1.xml represents the
>initial state, with all three managed servers (1, 2, and 3) running,
>and
>server1 currently hosting the JMS server.
>
>If I stop server1 and migrate to server2, using the following command:
>
>java weblogic.Admin -url localhost:7001 -username system -password security
>MIGRATE -migratabletarget "server1 (migratable)" -destination
>server2 -sourcedown
>
>then it succeeds, and you have config_2.xml.
>
>If I stop server2, restart server1, and try to migrate back to server1
>(using the same command, but reversing server1 and server2) then it doesn't
>work and I get the following message:
>
>Start server side stack trace:
>weblogic.management.runtime.MigrationException: Cannot migrate - destination
>server must not be the currently activate s
>erver - services are already deployed on that server.
> at
>weblogic.management.migration.MigrationTask.failWith(MigrationTask.java:728)
> at
>weblogic.management.migration.MigrationTask.check(MigrationTask.java:722)
> at
>weblogic.management.migration.MigrationTask.migrate(MigrationTask.java:258)
> at
>weblogic.management.migration.MigrationTask.access$7(MigrationTask.java:244)
> at
>weblogic.management.migration.MigrationTask$1.execute(MigrationTask.java:89)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>End server side stack trace
>
>and config file looks like config_3.xml
>
>Thanks for looking at this, it is much appreciated.
>
>Stanley.
>
>"Dongbo Xiao" <[email protected]> wrote in message
>news:[email protected]...
>> I may be able to help you more if you could send the config.xml (after
>> one migration) and the command you used for the migration.
>>
>> Dongbo
>>
>> Stanley Beamish wrote:
>>
>> > This is exactly the sort of thing I am seeing when using the command
>line.
>> > It definitely does not work correctly.
>> >
>> > SB
>> >
>> > "Anil Jacob" <[email protected]> wrote in message
>> > news:[email protected]...
>> > >
>> > > Dongbo,
>> > > What would happen when we use the commandline, In my case whether
>I
>> > migrate from
>> > > s1 to s2(example) it says s2 is already hosting these services
>and
>> > migration fails.
>> > > If I shutdown s1 and start s2 and try to migrate it still says
>the
>same
>> > thing.
>> > > Also I noticed the all of my destinations do not get migrated.
>> > >
>> > > Can you advice?
>> > >
>> > > thanks
>> > > Anil
>> > >
>> > > Dongbo Xiao <[email protected]> wrote:
>> > > >I suspect that the confusions you experienced comes from the names
>of
>> > > >the default migratable targets. If you have three managed servers
>> > > >(say s1, s2, and s3) in a cluster, by default, there will be three
>> > migratable
>> > > >targets: "s1 (migratable)", "s2 (migratable)", and "s3 (migratable)".
>> > > >For migratable target "s1 (migratable)", the candidate servers
>are
>s1,
>> > > >s2, and
>> > > >s3, and the user preferred server is s1 (which is by default the
>server
>> > > >hosting
>> > > >the services that are targeted to this migratable target).
>> > > >For migratable target "s2 (migratable)", the candidate servers
>are
>s1,
>> > > >s2, and
>> > > >s3, and the user preferred server is s2 (which is by default the
>server
>> > > >hosting
>> > > >he services that are targeted to this migratable target).
>> > > >
>> > > >If you target a JMS server to migratable target "s1 (migratable)",
>by
>> > > >default,
>> > > >the JMS server will be active on s1. You can migrate the JMS server
>to
>> > > >s2 or s3. After a migration, s2 (or s3) will be the user preferred
>> > server,
>> > > >but
>> > > >the migratable target is still named "s1 (migratable)". What you
>saw
>> > > >from the
>> > > >console after you hit Migrate button may be something like
>> > > >" Migration of s1 (migratable) to s2".
>> > > >
>> > > >If you migrate the JMS server from s2 back to s1, you may see:
>> > > >"Migration of s1 (migratable) to s1".
>> > > >
>> > > >You have to go to s1/Control/JMS Migrate to do all migrations
>for
>> > > >"s1 (migratable)", and go to s2/Control/JMS Migrate to do all
>> > > >migrations for "s2 (migratable)".
>> > > >
>> > > >Dongbo, BEA
>> > > >
>> > > >
>> > > >
>> > > >Stanley Beamish wrote:
>> > > >
>> > > >> Hi,
>> > > >>
>> > > >> I have a cluser with three managed nodes. I am experimenting
>with
>> > > >manual
>> > > >> migration of JMS services when the 'active' server goes down.
> The
>> > > >behaviour
>> > > >> it exhibits is distrinctly odd. If I kill the active server,
>and
>try
>> > > >to use
>> > > >> the console to migrate, then the various servers never seem
>to be
>able
>> > > >to
>> > > >> agree on what the current server is. server1 thinks its server1
>(which
>> > > >it
>> > > >> is). Server2 and 3 seem to think it's server2. If I migrate
>from
>> > > >the (now
>> > > >> killed) active server to an active one, by navigating to
>> > > >> server1/control/Migrate, then I get the option to migrate from
>server1
>> > > >to
>> > > >> server 2. If I confirm I want to do this, then it says migrating
>from
>> > > >> server1 to server1!!! WLS generally seems to get very confused
>as
>> > > >to which
>> > > >> is the current servers, and which servers can be the migration
>target.
>> > > > If I
>> > > >> start with a fresh cluster, with 3 managed nodes, and start
>up the
>> > > >admin
>> > > >> server and 2 of the managed nodes, then WLS (rather bizzarly)
>chooses
>> > > >the
>> > > >> third (not started) node as the one to associate the JMS services
>with!
>> > > > If
>> > > >> I try to use the command line utility (weblogic.Admin) to migrate
>> > instead
>> > > >of
>> > > >> using the console, then things get even worse. It will only
>correctly
>> > > >> peform the migration rarely. It often tells me that the target
>server
>> > > >that
>> > > >> I'm migrating to is already the active one (which it isn't).
> Even
>> > > >worse -
>> > > >> it often says 'OK' but in fact non of the servers are then hosting
>> > > >the JMS
>> > > >> service.
>> > > >>
>> > > >> Anybody else experienced these sorts of migration issues. I've
>tried
>> > > >this
>> > > >> with WLS 7.0 SP1 and WLS 7.0 SP2, and WLS 8.1 SP1 and they all
>exhibit
>> > > >the
>> > > >> same behaviour.
>> > > >>
>> > > >> Cheers,
>> > > >>
>> > > >> Stanley.
>> > > >
>> > >
>>
>
>
>begin 666 config_3.xml
>M/#]X;6P@=F5R<VEO;CTB,2XP(B!E;F-O9&EN9STB551&+3@B/SX*/"$M+4QA
>M<W0@=7!D871E9"!O;CH@1G)I($UA>2 S," Q,SHQ-3HT."!01%0@,C P,RP@
>M268@>6]U<B!D;VUA:6X@:7,@86-T:79E+"!P;&5A<V4@9&\@;F]T(&5D:70@
>M=&AE(&-O;F9I9RYX;6P@9FEL92X@06YY(&-H86YG97,@;6%D92!T;R!T:&%T
>M(&9I;&4@=VAI;&4@=&AE(&1O;6%I;B!I<R!A8W1I=F4@=VEL;"!N;W0@:&%V
>M92!A;GD@969F96-T(&]N('1H92!D;VUA:6XG<R!C;VYF:6=U<F%T:6]N(&%N
>M9"!A<F4@;&EK96QY('1O(&)E(&QO<W0N($EF('EO=7(@9&]M86EN(&ES(&EN
>M86-T:79E+"!Y;W4@;6%Y(&5D:70@=&AI<R!F:6QE('=I=&@@86X@6$U,(&5D
>M:71O<BX@268@>6]U(&1O('-O+"!P;&5A<V4@<F5F97(@=&\@=&AE($)%02!7
>M96)L;V=I8R!397)V97(@0V]N9FEG=7)A=&EO;B!2969E<F5N8V4@(&1O8W5M
>M96YT871I;VX@879A:6QA8FQE(&9R;VT@:'1T<#HO+V5D;V-S+F)E82YC;VTO
>M=VQS+V1O8W,W,"]C;VYF:6=?>&UL+B @26X@9V5N97)A;"P@=V4@<F5C;VUM
>M96YD('1H870@8VAA;F=E<R!T;R!Y;W5R(&-O;F9I9W5R871I;VX@9FEL92!B
>M92!M861E('1H<F]U9V@@=&AE($%D;6EN:7-T<F%T:6]N($-O;G-O;&4N+2T^
>M"CQ$;VUA:6X@0V]N9FEG=7)A=&EO;E9E<G-I;VX](C<N,"XR+C B($YA;64]
>M(F-L=7-T97)D;VUA:6XB/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)$969A=6QT5V5B07!P(@H@(" @(" @(%!A=&@](BY<87!P
>M;&EC871I;VYS(B!3=&%G961487)G971S/2(B(%1W;U!H87-E/2)F86QS92(^
>M"B @(" @(" @/%=E8D%P<$-O;7!O;F5N="!.86UE/2)$969A=6QT5V5B07!P
>M(B!487)G971S/2)M>7-E<G9E<B(@55))/2)$969A=6QT5V5B07!P(B\^"B @
>M(" \+T%P<&QI8V%T:6]N/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)?87!P<V1I<E]!8V-O=6YT14I"7VIA<B(*(" @(" @("!0
>M871H/2)'.EQB96$S7'5S97)?<')O:F5C='-<8VQU<W1E<F1O;6%I;EQA<'!L
>M:6-A=&EO;G,B"B @(" @(" @4W1A9V5D5&%R9V5T<STB<V5R=F5R,RQS97)V
>M97(Q+'-E<G9E<C(B(%-T86=I;F=-;V1E/2)S=&%G92(@5'=O4&AA<V4](G1R
>M=64B/@H@(" @(" @(#Q%2D)#;VUP;VYE;G0@3F%M93TB06-C;W5N=$5*0B(@
>M5&%R9V5T<STB;7EC;'5S=&5R(B!54DD](D%C8V]U;G1%2D(N:F%R(B\^"B @
>M(" \+T%P<&QI8V%T:6]N/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)C97)T:69I8V%T92(*(" @(" @("!0871H/2(N7&%P<&QI
>M8V%T:6]N<R(@4W1A9V5D5&%R9V5T<STB(B!4=V]0:&%S93TB9F%L<V4B/@H@
>M(" @(" @(#Q796)!<'!#;VUP;VYE;G0@3F%M93TB8V5R=&EF:6-A=&4B(%1A
>M<F=E=',](FUY<V5R=F5R(B!54DD](F-E<G1I9FEC871E+G=A<B(O/@H@(" @
>M/"]!<'!L:6-A=&EO;CX*(" @(#Q!<'!L:6-A=&EO;DUA;F%G97(@3F%M93TB
>M8VQU<W1E<F1O;6%I;B(O/@H@(" @/$-L=7-T97(*(" @(" @("!#;'5S=&5R
>M061D<F5S<STB;&]C86QH;W-T.C<Q,#$L;&]C86QH;W-T.C<R,#$L=&ES;F-L
>M,# Q.C<P,#$B"B @(" @(" @375L=&EC87-T061D<F5S<STB,C,W+C N,"XQ
>M(B!-=6QT:6-A<W10;W)T/2(W-S<W(B!.86UE/2)M>6-L=7-T97(B+SX*(" @
>M(#Q%;6)E9&1E9$Q$05 *(" @(" @("!#<F5D96YT:6%L/2)[,T1%4WU'>750
>M5D-J,VTK6'AT-DE'3G)6:#AG*S5!:&=J4F<P,VA$;%103S1Y<D1K/2(@3F%M
>M93TB8VQU<W1E<F1O;6%I;B(O/@H@(" @/$9I;&5296%L;2!.86UE/2)W;%]D
>M969A=6QT7V9I;&5?<F5A;&TB+SX*(" @(#Q*1$)#0V]N;F5C=&EO;E!O;VP*
>M(" @(" @("!$<FEV97).86UE/2)C;VTN<&]I;G1B87-E+FID8F,N:F1B8U5N
>M:79E<G-A;$1R:79E<B(*(" @(" @("!.86UE/2)"86YK4&]O;"(@4')O<&5R
>M=&EE<STB=7-E<CU00E!50DQ)0SMP87-S=V]R9#U00E!50DQ)0R(*(" @(" @
>M("!487)G971S/2)M>6-L=7-T97(B(%1E<W1#;VYN96-T:6]N<T]N4F5S97)V
>M93TB=')U92(*(" @(" @("!497-T5&%B;&5.86UE/2)B86YK+F%C8V]U;G0B
>M(%523#TB:F1B8SIP;VEN=&)A<V4Z<V5R=F5R.B\O;&]C86QH;W-T.CDP.3(O
>M8F%N:R(O/@H@(" @/$I$0D-#;VYN96-T:6]N4&]O; H@(" @(" @($1R:79E
>M<DYA;64](F-O;2YP;VEN=&)A<V4N:F1B8RYJ9&)C56YI=F5R<V%L1')I=F5R
>M(@H@(" @(" @($YA;64](E1)4TY#3# P,5]"86YK4&]O;"(*(" @(" @("!0
>M<F]P97)T:65S/2)U<V5R/5!"4%5"3$E#.W!A<W-W;W)D/5!"4%5"3$E#(B!4
>M87)G971S/2)M>6-L=7-T97(B"B @(" @(" @5&5S=$-O;FYE8W1I;VYS3VY2
>M97-E<G9E/2)T<G5E(B!497-T5&%B;&5.86UE/2)B86YK+F%C8V]U;G0B(%52
>M3#TB:F1B8SIP;VEN=&)A<V4Z<V5R=F5R.B\O=&ES;F-L,# Q.CDP.3(O8F%N
>M:R(O/@H@(" @/$I$0D-4>$1A=&%3;W5R8V4@2DY$24YA;64](D)A;FM$4R(@
>M3F%M93TB0F%N:T13(@H@(" @(" @(%!O;VQ.86UE/2)425-.0TPP,#%?0F%N
>M:U!O;VPB(%1A<F=E=',](FUY8VQU<W1E<B(O/@H@(" @/$I-4T1I<W1R:6)U
>M=&5D475E=64@1F]R=V%R9$1E;&%Y/2(U(B!*3D1)3F%M93TB1&ES=%%U975E
>M(@H@(" @(" @($YA;64](D1I<W11=65U92(@5&%R9V5T<STB;7EC;'5S=&5R
>M(CX*(" @(" @(" \2DU31&ES=')I8G5T9611=65U94UE;6)E<B!*35-1=65U
>M93TB475E=64Q(B!.86UE/2)->41I<W1R:6)U=&5D(%%U975E($UE;6)E<B(O
>M/@H@(" @(" @(#Q*35-$:7-T<FEB=71E9%%U975E365M8F5R($I-4U%U975E
>M/2)1=65U93(B($YA;64](DUY1&ES=')I8G5T960@475E=64@365M8F5R+3$B
>M+SX*(" @(" @(" \2DU31&ES=')I8G5T9611=65U94UE;6)E<B!*35-1=65U
>M93TB475E=64S(B!.86UE/2)->41I<W1R:6)U=&5D(%%U975E($UE;6)E<BTR
>M(B\^"B @(" @(" @/$I-4U1E;7!L871E($YA;64](D1I<W11=65U92(O/@H@
>M(" @/"]*35-$:7-T<FEB=71E9%%U975E/@H@(" @/$I-4T9I;&53=&]R92!$
>M:7)E8W1O<GD](D@Z7'1M<%QJ;7-<(B!.86UE/2)"86YK365S<V%G95-T;W)E
>M(B!3>6YC:')O;F]U<U=R:71E4&]L:6-Y/2)$:7)E8W0M5W)I=&4B+SX*(" @
>M(#Q*35-&:6QE4W1O<F4@1&ER96-T;W)Y/2)H.EQT;7!<:FUS(B!.86UE/2)M
>M97-S86=E4W1O<F4B(%-Y;F-H<F]N;W5S5W)I=&50;VQI8WD](D1I<F5C="U7
>M<FET92(O/@H@(" @/$I-4T9I;&53=&]R92!$:7)E8W1O<GD](F@Z7'1M<%QJ
>M;7,B($YA;64](G!A9VEN9U-T;W)E(B!3>6YC:')O;F]U<U=R:71E4&]L:6-Y
>M/2)$:7)E8W0M5W)I=&4B+SX*(" @(#Q*35-397)V97(@3F%M93TB2DU34V5R
>M=F5R,2(@5&%R9V5T<STB<V5R=F5R,2(^"B @(" @(" @/$I-4U%U975E($I.
>M1$E.86UE/2)1=65U93$B($YA;64](E%U975E,2(O/@H@(" @/"]*35-397)V
>M97(^"B @(" \2DU34V5R=F5R($YA;64](DI-4U-E<G9E<C(B(%1A<F=E=',]
>M(G-E<G9E<C(B/@H@(" @(" @(#Q*35-1=65U92!*3D1)3F%M93TB475E=64R
>M(B!.86UE/2)1=65U93(B+SX*(" @(#PO2DU34V5R=F5R/@H@(" @/$I-4U-E
>M<G9E<B!.86UE/2)*35-397)V97(S(B!487)G971S/2)S97)V97(S(CX*(" @
>M(" @(" \2DU3475E=64@2DY$24YA;64](E%U975E,R(@3F%M93TB475E=64S
>M(B\^"B @(" \+TI-4U-E<G9E<CX*(" @(#Q*35-397)V97(@3F%M93TB37E*
>M35-397)V97(B(%-T;W)E/2)"86YK365S<V%G95-T;W)E(B!487)G971S/2)S
>M97)V97(Q("AM:6=R871A8FQE*2(^"B @(" @(" @/$I-4U%U975E($I.1$E.
>M86UE/2)4<F%N<V9E<E)E<75E<W1S475E=64B($YA;64](E1R86YS9F5R475E
>M=64B+SX*(" @(#PO2DU34V5R=F5R/@H@(" @/$I402!.86UE/2)C;'5S=&5R
>M9&]M86EN(B\^"B @(" \3&]G($9I;&5.86UE/2(N7'=L+61O;6%I;BYL;V<B
>M($YA;64](F-L=7-T97)D;VUA:6XB+SX*(" @(#Q-86-H:6YE($YA;64](F-A
>M<G1M86XB/@H@(" @(" @(#Q.;V1E36%N86=E<B!.86UE/2)C87)T;6%N(B\^
>M"B @(" \+TUA8VAI;F4^"B @(" \36%C:&EN92!.86UE/2)T:7-N8VPP,#$B
>M/@H@(" @(" @(#Q.;V1E36%N86=E<B!,:7-T96Y!9&1R97-S/2)T:7-N8VPP
>M,#$B($YA;64](G1I<VYC;# P,2(O/@H@(" @/"]-86-H:6YE/@H@(" @/$UI
>M9W)A=&%B;&5487)G970@0VQU<W1E<CTB;7EC;'5S=&5R(B!.86UE/2)S97)V
>M97(Q("AM:6=R871A8FQE*2(*(" @(" @("!.;W1E<STB5&AI<R!I<R!A('-Y
>M<W1E;2!G96YE<F%T960@9&5F875L="!M:6=R871A8FQE('1A<F=E="!F;W(@
>M82!S97)V97(N($1O(&YO="!D96QE=&4@;6%N=6%L;'DN(B!5<V5R4')E9F5R
>M<F5D4V5R=F5R/2)S97)V97(R(B\^"B @(" \36EG<F%T86)L951A<F=E="!#
>M;'5S=&5R/2)M>6-L=7-T97(B($YA;64](G-E<G9E<C(@*&UI9W)A=&%B;&4I
>M(@H@(" @(" @($YO=&5S/2)4:&ES(&ES(&$@<WES=&5M(&=E;F5R871E9"!D
>M969A=6QT(&UI9W)A=&%B;&4@=&%R9V5T(&9O<B!A('-E<G9E<BX@1&\@;F]T
>M(&1E;&5T92!M86YU86QL>2XB(%5S97)0<F5F97)R961397)V97(](G-E<G9E
>M<C$B+SX*(" @(#Q-:6=R871A8FQE5&%R9V5T($-L=7-T97(](FUY8VQU<W1E
>M<B(@3F%M93TB<V5R=F5R,R H;6EG<F%T86)L92DB"B @(" @(" @3F]T97,]
>M(E1H:7,@:7,@82!S>7-T96T@9V5N97)A=&5D(&1E9F%U;'0@;6EG<F%T86)L
>M92!T87)G970@9F]R(&$@<V5R=F5R+B!$;R!N;W0@9&5L971E(&UA;G5A;&QY
>M+B(@57-E<E!R969E<G)E9%-E<G9E<CTB<V5R=F5R,2(O/@H@(" @/%!A<W-W
>M;W)D4&]L:6-Y($YA;64](G=L7V1E9F%U;'1?<&%S<W=O<F1?<&]L:6-Y(B\^
>M"B @(" \4F5A;&T@1FEL95)E86QM/2)W;%]D969A=6QT7V9I;&5?<F5A;&TB
>M($YA;64](G=L7V1E9F%U;'1?<F5A;&TB+SX*(" @(#Q33DU006=E;G0@3F%M
>M93TB8VQU<W1E<F1O;6%I;B(O/@H@(" @/%-E8W5R:71Y($=U97-T1&ES86)L
>M960](F9A;'-E(B!.86UE/2)C;'5S=&5R9&]M86EN(@H@(" @(" @(%!A<W-W
>M;W)D4&]L:6-Y/2)W;%]D969A=6QT7W!A<W-W;W)D7W!O;&EC>2(*(" @(" @
>M("!296%L;3TB=VQ?9&5F875L=%]R96%L;2(@4F5A;&U3971U<#TB=')U92(O
>M/@H@(" @/%-E8W5R:71Y0V]N9FEG=7)A=&EO;@H@(" @(" @($-R961E;G1I
>M86P](GLS1$53?3162&<K-7!13VU%;%AS2%HO6&HK0T-:-F134T$Y6G P<#4X
>M.7-U-$9L1DYM.'IR8C!K;W=Q46]12&Y$=SAB<$Y/,')3:$YO8TML3FE/;59*
>M2V%O-4YS:6AC5C)Z5C1M=R(@3F%M93TB8VQU<W1E<F1O;6%I;B(O/@H@(" @
>M/%-E<G9E<B!,:7-T96Y0;W)T/2(W,# Q(B!-86-H:6YE/2)C87)T;6%N(B!.
>M86UE/2)M>7-E<G9E<B(*(" @(" @("!.871I=F5)3T5N86)L960](G1R=64B
>M(%-E<G9E<E9E<G-I;VX](C<N,"XR+C B/@H@(" @(" @(#Q#3TT@3F%M93TB
>M;7ES97)V97(B+SX*(" @(" @(" \17AE8W5T95%U975E($YA;64](F1E9F%U
>M;'0B(%1H<F5A9$-O=6YT/2(Q-2(O/@H@(" @(" @(#Q)24]0($YA;64](FUY
>M<V5R=F5R(B\^"B @(" @(" @/$I404UI9W)A=&%B;&5487)G970@0VQU<W1E
>M<CTB(B!.86UE/2)M>7-E<G9E<B(@57-E<E!R969E<G)E9%-E<G9E<CTB;7ES
>M97)V97(B+SX*(" @(" @(" \2E1!4F5C;W9E<GE397)V:6-E($YA;64](FUY
>M<V5R=F5R(B\^"B @(" @(" @/$ME<FYE;$1E8G5G($YA;64](FUY<V5R=F5R
>M(B\^"B @(" @(" @/$QO9R!&:6QE3F%M93TB;7ES97)V97)<;7ES97)V97(N
>M;&]G(B!.86UE/2)M>7-E<G9E<B(O/@H@(" @(" @(#Q34TP@16YA8FQE9#TB
>M=')U92(@2&]S=&YA;65697)I9FEC871I;VY)9VYO<F5D/2)T<G5E(@H@(" @
>M(" @(" @("!,:7-T96Y0;W)T/2(W,# R(B!.86UE/2)M>7-E<G9E<B(*(" @
>M(" @(" @(" @4V5R=F5R0V5R=&EF:6-A=&5#:&%I;D9I;&5.86UE/2)C82YP
>M96TB"B @(" @(" @(" @(%-E<G9E<D-E<G1I9FEC871E1FEL94YA;64](F1E
>M;6]C97)T+G!E;2(@4V5R=F5R2V5Y1FEL94YA;64](F1E;6]K97DN<&5M(B\^
>M"B @(" @(" @/%-E<G9E<D1E8G5G($YA;64](FUY<V5R=F5R(B\^"B @(" @
>M(" @/%-E<G9E<E-T87)T($YA;64](FUY<V5R=F5R(B\^"B @(" @(" @/%=E
>M8E-E<G9E<B!$969A=6QT5V5B07!P/2)$969A=6QT5V5B07!P(@H@(" @(" @
>M(" @("!,;V=&:6QE3F%M93TB;7ES97)V97)<86-C97-S+FQO9R(@3&]G9VEN
>M9T5N86)L960](G1R=64B($YA;64](FUY<V5R=F5R(B\^"B @(" \+U-E<G9E
>M<CX*(" @(#Q397)V97(@075T;TMI;&Q)9D9A:6QE9#TB=')U92(@0VQU<W1E
>M<CTB;7EC;'5S=&5R(@H@(" @(" @($5X<&5C=&5D5&]2=6X](G1R=64B($AE
>M86QT:$-H96-K26YT97)V86Q396-O;F1S/2(V,"(*(" @(" @("!,:7-T96Y!
>M9&1R97-S/2)L;V-A;&AO<W0B($QI<W1E;E!O<G0](C<Q,#$B($UA8VAI;F4]
>M(F-A<G1M86XB"B @(" @(" @3F%M93TB<V5R=F5R,2(@3F%T:79E24]%;F%B
>M;&5D/2)T<G5E(B!297-T87)T1&5L87E396-O;F1S/2(U(B!397)V97)697)S
>M:6]N/2(W+C N,BXP(CX*(" @(" @(" \0T]-($YA;64](G-E<G9E<C$B+SX*
>M(" @(" @(" \17AE8W5T95%U975E($YA;64](F1E9F%U;'0B(%1H<F5A9$-O
>M=6YT/2(Q-2(O/@H@(" @(" @(#Q)24]0($YA;64](G-E<G9E<C$B+SX*(" @
>M(" @(" \2E1!36EG<F%T86)L951A<F=E="!#;'5S=&5R/2)M>6-L=7-T97(B
>M($YA;64](G-E<G9E<C$B(%5S97)0<F5F97)R961397)V97(](G-E<G9E<C$B
>M+SX*(" @(" @(" \2E1!4F5C;W9E<GE397)V:6-E($YA;64](G-E<G9E<C$B
>M+SX*(" @(" @(" \2V5R;F5L1&5B=6<@3F%M93TB<V5R=F5R,2(O/@H@(" @
>M(" @(#Q,;V<@3F%M93TB<V5R=F5R,2(O/@H@(" @(" @(#Q34TP@16YA8FQE
>M9#TB=')U92(@2&]S=&YA;65697)I9FEC871I;VY)9VYO<F5D/2)F86QS92(*
>M(" @(" @(" @(" @3&ES=&5N4&]R=#TB-S$P,B(@3F%M93TB<V5R=F5R,2(O
>M/@H@(" @(" @(#Q397)V97)$96)U9R!.86UE/2)S97)V97(Q(B\^"B @(" @
>M(" @/%-E<G9E<E-T87)T"B @(" @(" @(" @($%R9W5M96YT<STB+6AO='-P
>M;W0@+5AM<S,R;2 M6&UX,C P;2 M1'=E8FQO9VEC+G-E8W5R:71Y+E-33"YT
>M<G5S=&5D0T%+97E3=&]R93U'.EQB96$S7'=E8FQO9VEC-S P7'-E<G9E<EQL
>M:6)<8V%C97)T<R M1'=E8FQO9VEC+FUA;F%G96UE;G0N<V5R=F5R/29Q=6]T
>M.VAT=' Z+R]L;V-A;&AO<W0Z-S P,29Q=6]T.R M1'=E8FQO9VEC+E!R;V1U
>M8W1I;VY-;V1E16YA8FQE9#TB"B @(" @(" @(" @($)E84AO;64](D<Z7&)E
>M83,B"B @(" @(" @(" @($-L87-S4&%T:#TB1SI<8F5A,UQJ9&LQ,S%?,#9<
>M;&EB7'1O;VQS+FIA<CM'.EQB96$S7'=E8FQO9VEC-S P7'-E<G9E<EQL:6)<
>M=V5B;&]G:6-?<W N:F%R.T<Z7&)E83-<=V5B;&]G:6,W,#!<<V5R=F5R7&QI
>M8EQW96)L;V=I8RYJ87([1SI<8F5A,UQW96)L;V=I8S<P,%QS97)V97)<+BY<
>M<V%M<&QE<UQS97)V97)<979A;%QP;VEN=&)A<V5<;&EB7'!B8VQI96YT-#)%
>M0T8Q.#,N:F%R.T<Z7&)E83-<=V5B;&]G:6,W,#!<<V5R=F5R7"XN7'-A;7!L
>M97-<<V5R=F5R7&5V86Q<<&]I;G1B87-E7&QI8EQP8G-E<G9E<C0R14-&,3@S
>M+FIA<B(*(" @(" @(" @(" @2F%V84AO;64](D<Z7&)E83-<:F1K,3,Q7S V
>M(B!.86UE/2)S97)V97(Q(@H@(" @(" @(" @("!/=71P=71&:6QE/2)'.EQB
>M96$S7'5S97)?<')O:F5C='-<8VQU<W1E<F1O;6%I;EPN7$YO9&5-86YA9V5R
>M0VQI96YT3&]G<UQC;'5S=&5R9&]M86EN7W-E<G9E<C%<<W1A<G1S97)V97)?
>M,3 U-#$T-S Y-3 T-2YL;V<B"B @(" @(" @(" @(%!A<W-W;W)D/2)[,T1%
>M4WUA=3$Y15IJ2V%I9EE9=$QG<'=A8FAW/3TB"B @(" @(" @(" @(%)O;W1$
>M:7)E8W1O<GD](D<Z7&)E83-<=7-E<E]P<F]J96-T<UQC;'5S=&5R9&]M86EN
>M(@H@(" @(" @(" @("!396-U<FET>5!O;&EC>49I;&4](D<Z7&)E83-<=V5B
>M;&]G:6,W,#!<<V5R=F5R7&QI8EQW96)L;V=I8RYP;VQI8WDB(%5S97)N86UE
>M/2)S>7-T96TB+SX*(" @(" @(" \5V5B4V5R=F5R($YA;64](G-E<G9E<C$B
>M+SX*(" @(#PO4V5R=F5R/@H@(" @/%-E<G9E<B!!=71O2VEL;$EF1F%I;&5D
>M/2)T<G5E(B!#;'5S=&5R/2)M>6-L=7-T97(B"B @(" @(" @17AP96-T9614
>M;U)U;CTB=')U92(@2&5A;'1H0VAE8VM);G1E<G9A;%-E8V]N9',](C8P(@H@
>M(" @(" @($QI<W1E;D%D9')E<W,](FQO8V%L:&]S="(@3&ES=&5N4&]R=#TB
>M-S(P,2(@36%C:&EN93TB8V%R=&UA;B(*(" @(" @("!.86UE/2)S97)V97(R
>M(B!.871I=F5)3T5N86)L960](G1R=64B(%)E<W1A<G1$96QA>5-E8V]N9',]
>M(C$P(B!397)V97)697)S:6]N/2(W+C N,BXP(CX*(" @(" @(" \0T]-($YA
>M;64](G-E<G9E<C(B+SX*(" @(" @(" \17AE8W5T95%U975E($YA;64](F1E
>M9F%U;'0B(%1H<F5A9$-O=6YT/2(Q-2(O/@H@(" @(" @(#Q)24]0($YA;64]
>M(G-E<G9E<C(B+SX*(" @(" @(" \2E1!36EG<F%T86)L951A<F=E="!#;'5S
>M=&5R/2)M>6-L=7-T97(B($YA;64](G-E<G9E<C(B(%5S97)0<F5F97)R9613
>M97)V97(](G-E<G9E<C(B+SX*(" @(" @(" \2E1!4F5C;W9E<GE397)V:6-E
>M($YA;64](G-E<G9E<C(B+SX*(" @(" @(" \2V5R;F5L1&5B=6<@3F%M93TB
>M<V5R=F5R,B(O/@H@(" @(" @(#Q,;V<@3F%M93TB<V5R=F5R,B(O/@H@(" @
>M(" @(#Q34TP@16YA8FQE9#TB=')U92(@2&]S=&YA;65697)I9FEC871I;VY)
>M9VYO<F5D/2)F86QS92(*(" @(" @(" @(" @3&ES=&5N4&]R=#TB-S(P,B(@
>M3F%M93TB<V5R=F5R,B(O/@H@(" @(" @(#Q397)V97)$96)U9R!.86UE/2)S
>M97)V97(R(B\^"B @(" @(" @/%-E<G9E<E-T87)T"B @(" @(" @(" @($%R
>M9W5M96YT<STB+6AO='-P;W0@+5AM<S,R;2 M6&UX,C P;2 M1'=E8FQO9VEC
>M+G-E8W5R:71Y+E-33"YT<G5S=&5D0T%+97E3=&]R93U'.EQB96$S7'=E8FQO
>M9VEC-S P7'-E<G9E<EQL:6)<8V%C97)T<R M1'=E8FQO9VEC+DYA;64])G%U
>M;W0[<V5R=F5R,29Q=6]T.R @+41W96)L;V=I8RYM86YA9V5M96YT+G-E<G9E
>M<CTF<75O=#MH='1P.B\O;&]C86QH;W-T.C<P,#$F<75O=#L@+41W96)L;V=I
>M8RY0<F]D=6-T:6]N36]D945N86)L960](@H@(" @(" @(" @("!"96%(;VUE
>M/2)'.EQB96$S(@H@(" @(" @(" @("!#;&%S<U!A=&@](D<Z7&)E83-<:F1K
>M,3,Q7S V7&QI8EQT;V]L<RYJ87([1SI<8F5A,UQW96)L;V=I8S<P,%QS97)V
>M97)<;&EB7'=E8FQO9VEC7W-P+FIA<CM'.EQB96$S7'=E8FQO9VEC-S P7'-E
>M<G9E<EQL:6)<=V5B;&]G:6,N:F%R.T<Z7&)E83-<=V5B;&]G:6,W,#!<<V5R
>M=F5R7"XN7'-A;7!L97-<<V5R=F5R7&5V86Q<<&]I;G1B87-E7&QI8EQP8F-L
>M:65N=#0R14-&,3@S+FIA<CM'.EQB96$S7'=E8FQO9VEC-S P7'-E<G9E<EPN
>M+EQS86UP;&5S7'-E<G9E<EQE=F%L7'!O:6YT8F%S95QL:6)<<&)S97)V97(T
>M,D5#1C$X,RYJ87(B"B @(" @(" @(" @($IA=F%(;VUE/2)'.EQB96$S7&ID
>M:S$S,5\P-B(@3F%M93TB<V5R=F5R,B(*(" @(" @(" @(" @3W5T<'5T1FEL
>M93TB1SI<8F5A,UQU<V5R7W!R;VIE8W1S7&-L=7-T97)D;VUA:6Y<+EQ.;V1E
>M36%N86=E<D-L:65N=$QO9W-<8VQU<W1E<F1O;6%I;E]S97)V97(R7'-T87)T
>M<V5R=F5R7S$P-30Q-# R-C@V-SDN;&]G(@H@(" @(" @(" @("!087-S=V]R
>M9#TB>S-$15-]874Q.45::DMA:699671,9W!W86)H=ST](@H@(" @(" @(" @
>M("!2;V]T1&ER96-T;W)Y/2)'.EQB96$S7'5S97)?<')O:F5C='-<8VQU<W1E
>M<F1O;6%I;B(*(" @(" @(" @(" @4V5C=7)I='E0;VQI8WE&:6QE/2)'.EQB
>M96$S7'=E8FQO9VEC-S P7'-E<G9E<EQL:6)<=V5B;&]G:6,N<&]L:6-Y(B!5
>M<V5R;F%M93TB<WES=&5M(B\^"B @(" @(" @/%=E8E-E<G9E<B!.86UE/2)S
>M97)V97(R(B\^"B @(" \+U-E<G9E<CX*(" @(#Q397)V97(@0VQU<W1E<CTB
>M;7EC;'5S=&5R(B!%>'!E8W1E9%1O4G5N/2)T<G5E(@H@(" @(" @($QI<W1E
>M;D%D9')E<W,](G1I<VYC;# P,2(@3&ES=&5N4&]R=#TB-S P,2(@36%C:&EN
>M93TB=&ES;F-L,# Q(@H@(" @(" @($YA;64](G-E<G9E<C,B($YA=&EV94E/
>M16YA8FQE9#TB=')U92(@4V5R=F5R5F5R<VEO;CTB-RXP+C(N,"(^"B @(" @
>M(" @/$-/32!.86UE/2)S97)V97(S(B\^"B @(" @(" @/$5X96-U=&51=65U
>M92!.86UE/2)D969A=6QT(B!4:')E861#;W5N=#TB,34B+SX*(" @(" @(" \
>M24E/4"!.86UE/2)S97)V97(S(B\^"B @(" @(" @/$I404UI9W)A=&%B;&54
>M87)G970@0VQU<W1E<CTB;7EC;'5S=&5R(B!.86UE/2)S97)V97(S(B!5<V5R
>M4')E9F5R<F5D4V5R=F5R/2)S97)V97(S(B\^"B @(" @(" @/$I405)E8V]V
>M97)Y4V5R=FEC92!.86UE/2)S97)V97(S(B\^"B @(" @(" @/$ME<FYE;$1E
>M8G5G($YA;64](G-E<G9E<C,B+SX*(" @(" @(" \3&]G($YA;64](G-E<G9E
>M<C,B+SX*(" @(" @(" \4U-,($5N86)L960](G1R=64B($AO<W1N86UE5F5R
>M:69I8V%T:6]N26=N;W)E9#TB9F%L<V4B"B @(" @(" @(" @($QI<W1E;E!O
>M<G0](C<P,#(B($YA;64](G-E<G9E<C,B+SX*(" @(" @(" \4V5R=F5R1&5B
>M=6<@3F%M93TB<V5R=F5R,R(O/@H@(" @(" @(#Q397)V97)3=&%R= H@(" @
>M(" @(" @("!!<F=U;65N=',](BUH;W1S<&]T("U8;7,S,FT@+5AM>#(P,&T@
>M+41W96)L;V=I8RYS96-U<FET>2Y34TPN=')U<W1E9$-!2V5Y4W1O<F4]1SI<
>M8F5A-%QW96)L;V=I8S<P,%QS97)V97)<;&EB7&-A8V5R=',@+41W96)L;V=I
>M8RYM86YA9V5M96YT+G-E<G9E<CTF<75O=#MH='1P.B\O;&]C86QH;W-T.C<P
>M,#$F<75O=#L@+41W96)L;V=I8RY0<F]D=6-T:6]N36]D945N86)L960]9F%L
>M<V4B"B @(" @(" @(" @($)E84AO;64](D<Z7&)E830B"B @(" @(" @(" @
>M($-L87-S4&%T:#TB1SI<8F5A-%QJ9&LQ,S%?,#9<;&EB7'1O;VQS+FIA<CM'
>M.EQB96$T7'=E8FQO9VEC-S P7'-E<G9E<EQL:6)<=V5B;&]G:6-?<W N:F%R
>M.T<Z7&)E831<=V5B;&]G:6,W,#!<<V5R=F5R7&QI8EQW96)L;V=I8RYJ87([
>M1SI<8F5A-%QW96)L;V=I8S<P,%QS97)V97)<+BY<<V%M<&QE<UQS97)V97)<
>M979A;%QP;VEN=&)A<V5<;&EB7'!B8VQI96YT-#)%0T8Q.#,N:F%R.T<Z7&)E
>M831<=V5B;&]G:6,W,#!<<V5R=F5R7"XN7'-A;7!L97-<<V5R=F5R7&5V86Q<
>M<&]I;G1B87-E7&QI8EQP8G-E<G9E<C0R14-&,3@S+FIA<B(*(" @(" @(" @
>M(" @2F%V84AO;64](D<Z7&)E831<:F1K,3,Q7S V(B!.86UE/2)S97)V97(S
>M(@H@(" @(" @(" @("!/=71P=71&:6QE/2)'.EQB96$S7'5S97)?<')O:F5C
>M='-<8VQU<W1E<F1O;6%I;EPN7$YO9&5-86YA9V5R0VQI96YT3&]G<UQC;'5S
>M=&5R9&]M86EN7W-E<G9E<C-<<W1A<G1S97)V97)?,3 U-#$T,SDU,#DP-"YL
>M;V<B"B @(" @(" @(" @(%!A<W-W;W)D/2)[,T1%4WUA=3$Y15IJ2V%I9EE9
>M=$QG<'=A8FAW/3TB"B @(" @(" @(" @(%)O;W1$:7)E8W1O<GD](D<Z7&)E
>M831<=7-E<E]P<F]J96-T<UQC;'5S=&5R9&]M86EN(@H@(" @(" @(" @("!3
>M96-U<FET>5!O;&EC>49I;&4](D<Z7&)E831<=V5B;&]G:6,W,#!<<V5R=F5R
>M7&QI8EQW96)L;V=I8RYP;VQI8WDB(%5S97)N86UE/2)S>7-T96TB+SX*(" @
>M(" @(" \5V5B4V5R=F5R($YA;64](G-E<G9E<C,B+SX*(" @(#PO4V5R=F5R
>,/@H\+T1O;6%I;CX*
>`
>end
>
>begin 666 config_2.xml
>M/#]X;6P@=F5R<VEO;CTB,2XP(B!E;F-O9&EN9STB551&+3@B/SX*/"$M+4QA
>M<W0@=7!D871E9"!O;CH@1G)I($UA>2 S," Q,SHQ,SHP."!01%0@,C P,RP@
>M268@>6]U<B!D;VUA:6X@:7,@86-T:79E+"!P;&5A<V4@9&\@;F]T(&5D:70@
>M=&AE(&-O;F9I9RYX;6P@9FEL92X@06YY(&-H86YG97,@;6%D92!T;R!T:&%T
>M(&9I;&4@=VAI;&4@=&AE(&1O;6%I;B!I<R!A8W1I=F4@=VEL;"!N;W0@:&%V
>M92!A;GD@969F96-T(&]N('1H92!D;VUA:6XG<R!C;VYF:6=U<F%T:6]N(&%N
>M9"!A<F4@;&EK96QY('1O(&)E(&QO<W0N($EF('EO=7(@9&]M86EN(&ES(&EN
>M86-T:79E+"!Y;W4@;6%Y(&5D:70@=&AI<R!F:6QE('=I=&@@86X@6$U,(&5D
>M:71O<BX@268@>6]U(&1O('-O+"!P;&5A<V4@<F5F97(@=&\@=&AE($)%02!7
>M96)L;V=I8R!397)V97(@0V]N9FEG=7)A=&EO;B!2969E<F5N8V4@(&1O8W5M
>M96YT871I;VX@879A:6QA8FQE(&9R;VT@:'1T<#HO+V5D;V-S+F)E82YC;VTO
>M=VQS+V1O8W,W,"]C;VYF:6=?>&UL+B @26X@9V5N97)A;"P@=V4@<F5C;VUM
>M96YD('1H870@8VAA;F=E<R!T;R!Y;W5R(&-O;F9I9W5R871I;VX@9FEL92!B
>M92!M861E('1H<F]U9V@@=&AE($%D;6EN:7-T<F%T:6]N($-O;G-O;&4N+2T^
>M"CQ$;VUA:6X@0V]N9FEG=7)A=&EO;E9E<G-I;VX](C<N,"XR+C B($YA;64]
>M(F-L=7-T97)D;VUA:6XB/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)$969A=6QT5V5B07!P(@H@(" @(" @(%!A=&@](BY<87!P
>M;&EC871I;VYS(B!3=&%G961487)G971S/2(B(%1W;U!H87-E/2)F86QS92(^
>M"B @(" @(" @/%=E8D%P<$-O;7!O;F5N="!.86UE/2)$969A=6QT5V5B07!P
>M(B!487)G971S/2)M>7-E<G9E<B(@55))/2)$969A=6QT5V5B07!P(B\^"B @
>M(" \+T%P<&QI8V%T:6]N/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)?87!P<V1I<E]!8V-O=6YT14I"7VIA<B(*(" @(" @("!0
>M871H/2)'.EQB96$S7'5S97)?<')O:F5C='-<8VQU<W1E<F1O;6%I;EQA<'!L
>M:6-A=&EO;G,B"B @(" @(" @4W1A9V5D5&%R9V5T<STB<V5R=F5R,RQS97)V
>M97(Q+'-E<G9E<C(B(%-T86=I;F=-;V1E/2)S=&%G92(@5'=O4&AA<V4](G1R
>M=64B/@H@(" @(" @(#Q%2D)#;VUP;VYE;G0@3F%M93TB06-C;W5N=$5*0B(@
>M5&%R9V5T<STB;7EC;'5S=&5R(B!54DD](D%C8V]U;G1%2D(N:F%R(B\^"B @
>M(" \+T%P<&QI8V%T:6]N/@H@(" @/$%P<&QI8V%T:6]N($1E<&QO>65D/2)T
>M<G5E(B!.86UE/2)C97)T:69I8V%T92(*(" @(" @("!0871H/2(N7&%P<&QI
>M8V%T:6]N<R(@4W1A9V5D5&%R9V5T<STB(B!4=V]0:&%S93TB9F%L<V4B/@H@
>M(" @(" @(#Q796)!<'!#;VUP;VYE;G0@3F%M93TB8V5R=&EF:6-A=&4B(%1A
>M<F=E=',](FUY<V5R=F5R(B!54DD](F-E<G1I9FEC871E+G=A<B(O/@H@(" @
>M/"]!<'!L:6-A=&EO;CX*(" @(#Q!<'!L:6-A=&EO;DUA;F%G97(@3F%M93TB
>M8VQU<W1E<F1O;6%I;B(O/@H@(" @/$-L=7-T97(*(" @(" @("!#;'5S=&5R
>M061D<F5S<STB;&]C86QH;W-T.C<Q,#$L;&]C86QH;W-T.C<R,#$L=&ES;F-L
>M,# Q.C<P,#$B"B @(" @(" @375L=&EC87-T061D<F5S<STB,C,W+C N,"XQ
>M(B!-=6QT:6-A<W10;W)T/2(W-S<W(B!.86UE/2)M>6-L=7-T97(B+SX*(" @
>M(#Q%;6)E9&1E9$Q$05 *(" @(" @("!#<F5D96YT:6%L/2)[,T1%4WU'>750
>M5D-J,VTK6'AT-DE'3G)6:#AG*S5!:&=J4F<P,VA$;%103S1Y<D1K/2(@3F%M
>M93TB8VQU<W1E<F1O;6%I;B(O/@H@(" @/$9I;&5296%L;2!.86UE/2)W;%]D
>M969A=6QT7V9I;&5?<F5A;&TB+SX*(" @(#Q*1$)#0V]N;F5C=&EO;E!O;VP*
>M(" @(" @("!$<FEV97).86UE/2)C;VTN<&]I;G1B87-E+FID8F,N:F1B8U5N
>M:79E<G-A;$1R:79E<B(*(" @(" @("!.86UE/2)"86YK4&]O;"(@4')O<&5R
>M=&EE<STB=7-E<CU00E!50DQ)0SMP87-S=V]R9#U00E!50DQ)0R(*(" @(" @
>M("!487)G971S/2)M>6-L=7-T97(B(%1E<W1#;VYN96-T:6]N<T]N4F5S97)V
>M93TB=')U92(*(" @(" @("!497-T5&%B;&5.86UE/2)B86YK+F%C8V]U;G0B
>M(%523#TB:F1B8SIP;VEN=&)A<V4Z<V5R=F5R.B\O;&]C86QH;W-T.CDP.3(O
>M8F%N:R(O/@H@(" @/$I$0D-#;VYN96-T:6]N4&]O; H@(" @(" @($1R:79E
>M<DYA;64](F-O;2YP;VEN=&)A<V4N:F1B8RYJ9&)C56YI=F5R<V%L1')I=F5R
>M(@H@(" @(" @($YA;64](E1)4TY#3# P,5]"86YK4&]O;"(*(" @(" @("!0
>M<F]P97)T:65S/2)U<V5R/5!"4%5"3$E#.W!A<W-W;W)D/5!"4%5"3$E#(B!4
>M87)G971S/2)M>6-L=7-T97(B"B @(" @(" @5&5S=$-O;FYE8W1I;VYS3VY2
>M97-E<G9E/2)T<G5E(B!497-T5&%B;&5.86UE/2)B86YK+F%C8V]U;G0B(%52
>M3#TB:F1B8SIP;VEN=&)A<V4Z<V5R=F5R.B\O=&ES;F-L,# Q.CDP.3(O8F%N
>M:R(O/@H@(" @/$I$0D-4>$1A=&%3;W5R8V4@2DY$24YA;64](D)A;FM$4R(@
>M3F%M93TB0F%N:T13(@H@(" @(" @(%!O;VQ.86UE/2)425-.0TPP,#%?0F%N
>M:U!O;VPB(%1A<F=E=',](FUY8VQU<W1E<B(O/@H@(" @/$I-4T1I<W1R:6)U
>M=&5D475E=64@1F]R=V%R9$1E;&%Y/2(U(B!*3D1)3F%M93TB1&ES=%%U975E
>M(@H@(" @(" @($YA;64](D1I<W11=65U92(@5&%R9V5T<STB;7EC;'5S=&5R
>M(CX*(" @(" @(" \2DU31&ES=')I8G5T9611=65U94UE;6)E<B!*35-1=65U
>M93TB475E=64Q(B!.86UE/2)->41I<W1R:6)U=&5D(%%U975E($UE;6)E<B(O
>M/@H@(" @(" @(#Q*35-$:7-T<FEB=71E9%%U975E365M8F5R($I-4U%U975E
>M/2)1=65U93(B($YA;64](DUY1&ES=')I8G5T960@475E=64@365M8F5R+3$B
>M+SX*(" @(" @(" \2DU31&ES=')I8G5T9611=65U94UE;6)E<B!*35-1=65U
>M93TB475E=64S(B!.86UE/2)->41I<W1R:6)U=&5D(%%U975E($UE;6)E<BTR
>M(B\^"B @(" @(" @/$I-4U1E;7!L871E($YA;64](D1I<W11=65U92(O/@H@
>M(" @/"]*35-$:7-T<FEB=71E9%%U975E/@H@(" @/$I-4T9I;&53=&]R92!$
>M:7)E8W1O<GD](D@Z7'1M<%QJ;7-<(B!.86UE/2)"86YK365S<V%G95-T;W)E
>M(B!3>6YC:')O;F]U<U=R:71E4&]L:6-Y/2)$:7)E8W0M5W)I=&4B+SX*(" @
>M(#Q*35-&:6QE4W1O<F4@1&ER96-T;W)Y/2)H.EQT;7!<:FUS(B!.86UE/2)M
>M97-S86=E4W1O<F4B(%-Y;F-H<F]N;W5S5W)I=&50;VQI8WD](D1I<F5C="U7
>M<FET92(O/@H@(" @/$I-4T9I;&53=&]R92!$:7)E8W1O<GD](F@Z7'1M<%QJ
>M;7,B($YA;64](G!A9VEN9U-T;W)E(B!3>6YC:')O;F]U<U=R:71E4&]L:6-Y
>M/2)$:7)E8W0M5W)I=&4B+SX*(" @(#Q*35-397)V97(@3F%M93TB2DU34V5R
>M=F5R,2(@5&%R9V5T<STB<V5R=F5R,2(^"B @(" @(" @/$I-4U%U975E($I.
>M1$E.86UE/2)1=65U93$B($YA;64](E%U975E,2(O/@H@(" @/"]*35-397)V
>M97(^"B @(" \2DU34V5R=F5R($YA;64](DI-4U-E<G9E<C(B(%1A<F=E=',]
>M(G-E<G9E<C(B/@H@(" @(" @(#Q*35-1=65U92!*3D1)3F%M93TB475E=64R
>M(B!.86UE/2)1=65U93(B+SX*(" @(#PO2DU34V5R=F5R/@H@(" @/$I-4U-E
>M<G9E<B!.86UE/2)*35-397)V97(S(B!487)G971S/2)S97)V97(S(CX*(" @
>M(" @(" \2DU3475E=64@2DY$24YA;64](E%U975E,R(@3F%M93TB475E=64S
>M(B\^"B @(" \+TI-4U-E<G9E<CX*(" @(#Q*35-397)V97(@3F%M93TB37E*
>M35-397)V97(B(%-T;W)E/2)"86YK365S<V%G95-T;W)E(B!487)G971S/2)S
>M97)V97(Q("AM -
SetStringProperty in JMS receiver adapter doesn't work
I want to set a property in the RFH2-header to my MQ-message but it doesn't work.
I try to do this by setting the additional JMS Parameter "JMS.Message.method.setStringProperty" but nothing happens in the resulting MQ-message.
The resulting MQ-message (the header) looks like this.
(0x01000000):MQRFH2 = (
(0x03000000):Version = 2
(0x03000000):Format = 'MQSTR '
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 1208
(0x03000000):Flags = 0
(0x03000000):NameValueCCSID = 1208
(0x01000000):mcd = (
(0x01000000):Msd = (
(0x02000000): = 'jms_text'
(0x01000000):jms = (
(0x01000000):Dst = (
(0x02000000): = 'queue:///SOMEQ'
(0x01000000):Tms = (
(0x02000000): = '1180524893525'
(0x01000000):Cid = (
(0x02000000): = '465c8ee5-91a5-00ae-0000-0000c0a82364'
(0x01000000):Dlv = (
(0x02000000): = '2'
Where can I expect to see my assigned property? I thought it should show up like below.
(0x01000000):usr = (
(0x01000000):MyProperty = (
(0x02000000): = 'MyValue'
Can somebody please help me?
regards
/HeléDid you solve your issue? If so, could you please share? I'm facing a similar problem.
Thanks
Cheers
Jens -
My J2EE 1.4 SDK installation doesn't work (j2eesdk-1_4_03-windows.exe)
Hi!
I think that this is a very curious case. The preparation of the installation is completely right (it loads the Java(TM) 2 Runtime Environment, extract the files). The first screen appears and I click on next, I agree with the software license and click to go next. In the third screen is where the matter happens, I leave the default Installation Directory (C:\Sun\AppServer) and click on next button but the interface is frozen, not more screens are shown, I can move the mouse and even I can execute perfectly the button Browse, and minimize, maximize and close button but the bottom buttons line doesn't work (Back, Next, Cancel, Help), I have left the screen for hours and nothing happens, I only close the interface without installing the sdk.
I try to install j2eesdk-1_4_03-windows.exe on WIndows XP SP3 (before it was SP2 but I changed to test the install but it doesn't work too), I have installed the Java SE Runtime Environment 6 and Java (TM) Update 12, too I have the Java(TM) SE Development Kit 6 and J2ME Wireless Toolkit 2.2, all of them without problems.
I put a link to my frozen screen [http://img19.imageshack.us/img19/6911/j2ee14sdkinstalattionwi.jpg]
PD: sorry for my bad English.
Edited by: Paco-Spain on Mar 17, 2009 4:55 PMHi.
I had same problem on my PC today ...
Try to find and delete two files somewhere in c:\windows\...folders -
productregistry and productregistry.access.tmp -
Com.sap.portal.appintegrator.sap doesn't work
Hi all,
I needed to change the file 'WinGuiRenderLayer.properties'
I found the par under 3 locations:
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
I changed the file in those locations (I removed the bak extension and restarted the server).
Also, I made sure that the pars/directory contains the jar files.
After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
Before I did the changes, I backed up the original pars/directory.
Copying the original pars didn't help.
How can I solve this?
Portal is EP6.16
Attched exception details:
Date : 10/25/2007
Time : 13:56:51:765
Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Severity : Warning
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_27
Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Dsr Component : <Server Name>
Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
Dsr User : <User>
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 44
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_27
Transaction :
User : <User>
Thanks,
OmriSolved it.
This is what I did:
1) Took par from my production environment (same SP level)
2) Clear the par (by using 'Archive Remover')
3) Clear the pcd cache
4) Upload the par (redploy)\
5) Restart the portal
Thanks,
Omri -
Page naviagation doesn't work after deploy ADF application to Weblogic
After deploy my ADF application (ear) to Weblogic Server, the page navigation doesn't work. When running the ear on weblogic, I got following warnings:
<2010-11-5 下午05时06分01秒 CST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application HwtOrder is not versioned.>
<2010-11-5 下午05时06分38秒 CST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DHwtOrder%2CType%3DAppDeployment%22%29.>
<2010-11-5 下午05时07分33秒 CST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22DefaultServer%3BDomainLog%22%29.>
I can run the application correctly in jdeveloper 11g environment. I think there is something wrong with deployment. Can anyone help me?When you target url with .jspx, you are running the page itself, not in the task flow context, so navigation doesn't work.
In the task flow, your page has 'Activity ID' (which is, for example, 'mainPage' for mainPage.jspx) and the navigation is defined for activity IDs, not pages.
Pedja -
RFC Sender (XI 3.0, SP14) Load Balancing doesn't work
Hi all,
We're "desperately" trying to use the Load Balancing option of RFC Sender Adapter (XI 3.0, SP14). It doesn't work.
The Adapter can not register to the sender SAP server. But when we do not use the "Load Balancing" option, everything works well.
We did follow the XI guidelines step-by-step. All necessary configurations in XI and in SAP sender system (TA: SM59) are "properly" done and reviewed by different experts several times.
Do you have, by chance any running scenario using "Load Balancing" within a RFC Adapter? If yes, I would appreciate if you can share it with me.
Thanks a lot!
Regards,
KhaledHello Khaled,
the RFC sender adapter registers a program at the SAP Gateway. Load Balancing for the Sender Adapter means, that you have at least two J2EE server nodes within your XI installation. On all these server nodes the same RFC sender adapter is started and register the same program at the same gateway. The load balancing is then handled by the gateway. That means, that for the sender adapter the settings are the same, even if you use load balancing or not.
The settings are, e.g.
- SID=ABC
- hostname=abchost (central instance, message server)
- hostname=xyzhost (additional dialog instance of ABC)
- instance nr=00
application server (gateway): xi1host
application server service (gw-service): sapgw00
programm id: could be freely choosen
The Metadata Repository could be connected using load balancing. Here a user need to log on to the system.
The settings here must be:
Message-Server: abchost
Message-Server-Service: sapmsABC
System-ID: ABC
Logon-Group: e.g. PUBLIC; this logon group need to be created in system ABC using transaction SMLG
For the RFC-Receiver Adapter the same settings as for the Metadata could be used.
Keep in mind, that for the RFC Sender Adapter a RFC connection of type T must be created in transaction SM59 in system ABC.
Rgds.,
Andreas -
ActiveDirectory mapping file, doesn't work for login
The mapping file below works.
Logged in as administrator, in the SAP NP administrator web tool,
I can see and edit users in the datasource (Active Directory).
However, when users in the AD try to login to the portal, they get "User authentication failed".
<u>Default trace log show:</u>
Authentication failed on LDAP server: back end message [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece]
and
java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key DS_AD_I
<b>Any ideas on what in the configuration file below,
that could cause these errors ?</b>
====================================
<b>Configuration file</b>
====================================
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: //shared_tc/com.sapall.security/630_SP_COR/src/_deploy/dist/configuration/shared/dataSourceConfiguration_ads_readonly_db.xml#6 $ from $DateTime: 2004/08/20 09:55:24 $ ($Change: 17140 $) -->
<!DOCTYPE dataSources SYSTEM "dataSourceConfiguration.dtd">
<dataSources>
<dataSource id="PRIVATE_DATASOURCE"
className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence"
isReadonly="false"
isPrimary="true">
<homeFor>
<principals>
<principal type="group"/>
<principal type="user"/>
<principal type="account"/>
<principal type="team"/>
<principal type="ROOT" />
<principal type="OOOO" />
</principals>
</homeFor>
<notHomeFor/>
<responsibleFor>
<principals>
<principal type="group"/>
<principal type="user"/>
<principal type="account"/>
<principal type="team"/>
<principal type="ROOT" />
<principal type="OOOO" />
</principals>
</responsibleFor>
<privateSection>
</privateSection>
</dataSource>
<dataSource id="AD_I"
className="com.sap.security.core.persistence.datasource.imp.LDAPPersistence"
isReadonly="false"
isPrimary="true">
<homeFor/>
<responsibleFor>
<principal type="account">
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="j_user"/>
<attribute name="logonalias"/>
<attribute name="j_password"/>
<attribute name="userid"/>
</attributes>
</nameSpace>
</principal>
<principal type="user">
<nameSpaces>
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="firstname" populateInitially="true"/>
<attribute name="displayname" populateInitially="true"/>
<attribute name="lastname" populateInitially="true"/>
<attribute name="fax"/>
<attribute name="email"/>
<attribute name="title"/>
<attribute name="department"/>
<attribute name="description"/>
<attribute name="mobile"/>
<attribute name="telephone"/>
<attribute name="streetaddress"/>
<attribute name="uniquename" populateInitially="true"/>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.usermanagement.relation">
<attributes>
<attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
</attributes>
</nameSpace>
<nameSpace name="$usermapping$">
<attributes>
<attribute name="REFERENCE_SYSTEM_USER"/>
</attributes>
</nameSpace>
</nameSpaces>
</principal>
<principal type="group">
<nameSpaces>
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="displayname" populateInitially="true"/>
<attribute name="description" populateInitially="true"/>
<attribute name="uniquename"/>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.usermanagement.relation">
<attributes>
<attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>
<attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE"/>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.bridge">
<attributes>
<attribute name="dn"/>
</attributes>
</nameSpace>
</nameSpaces>
</principal>
</responsibleFor>
<attributeMapping>
<principals>
<principal type="account">
<nameSpaces>
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="j_user">
<physicalAttribute name="samaccountname"/>
</attribute>
<attribute name="logonalias">
<physicalAttribute name="samaccountname"/>
</attribute>
<attribute name="j_password">
<physicalAttribute name="userPassword"/>
</attribute>
<attribute name="userid">
<physicalAttribute name="null"/>
</attribute>
</attributes>
</nameSpace>
</nameSpaces>
</principal>
<principal type="user">
<nameSpaces>
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="firstname">
<physicalAttribute name="givenname"/>
</attribute>
<attribute name="displayname">
<physicalAttribute name="displayname"/>
</attribute>
<attribute name="lastname">
<physicalAttribute name="sn"/>
</attribute>
<attribute name="fax">
<physicalAttribute name="facsimiletelephonenumber"/>
</attribute>
<attribute name="uniquename">
<physicalAttribute name="samaccountname"/>
</attribute>
<attribute name="loginid">
<physicalAttribute name="null"/>
</attribute>
<attribute name="email">
<physicalAttribute name="mail"/>
</attribute>
<attribute name="mobile">
<physicalAttribute name="mobile"/>
</attribute>
<attribute name="telephone">
<physicalAttribute name="telephonenumber"/>
</attribute>
<attribute name="department">
<physicalAttribute name="ou"/>
</attribute>
<attribute name="description">
<physicalAttribute name="description"/>
</attribute>
<attribute name="streetaddress">
<physicalAttribute name="postaladdress"/>
</attribute>
<attribute name="pobox">
<physicalAttribute name="postofficebox"/>
</attribute>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.usermanagement.relation">
<attributes>
<attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
<physicalAttribute name="memberof"/>
</attribute>
</attributes>
</nameSpace>
<nameSpace name="$usermapping$">
<attributes>
<attribute name="REFERENCE_SYSTEM_USER">
<physicalAttribute name="sapusername"/>
</attribute>
</attributes>
</nameSpace>
</nameSpaces>
</principal>
<principal type="group">
<nameSpaces>
<nameSpace name="com.sap.security.core.usermanagement">
<attributes>
<attribute name="displayname">
<physicalAttribute name="displayname"/>
</attribute>
<attribute name="description">
<physicalAttribute name="description"/>
</attribute>
<attribute name="uniquename" populateInitially="true">
<physicalAttribute name="cn"/>
</attribute>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.usermanagement.relation">
<attributes>
<attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE">
<physicalAttribute name="member"/>
</attribute>
<attribute name="PRINCIPAL_RELATION_PARENT_ATTRIBUTE">
<physicalAttribute name="memberof"/>
</attribute>
</attributes>
</nameSpace>
<nameSpace name="com.sap.security.core.bridge">
<attributes>
<attribute name="dn">
<physicalAttribute name="null"/>
</attribute>
</attributes>
</nameSpace>
</nameSpaces>
</principal>
</principals>
</attributeMapping>
<privateSection>
<ume.ldap.access.server_type>MSADS</ume.ldap.access.server_type>
<ume.ldap.access.context_factory>com.sun.jndi.ldap.LdapCtxFactory</ume.ldap.access.context_factory>
<ume.ldap.access.authentication>simple</ume.ldap.access.authentication>
<ume.ldap.access.flat_group_hierachy>true</ume.ldap.access.flat_group_hierachy>
<ume.ldap.access.user_as_account>true</ume.ldap.access.user_as_account>
<ume.ldap.access.dynamic_groups>false</ume.ldap.access.dynamic_groups>
<ume.ldap.access.ssl_socket_factory>com.sap.security.core.server.https.SecureConnectionFactory</ume.ldap.access.ssl_socket_factory>
<ume.ldap.access.server_name>machine.company.com</ume.ldap.access.server_name>
<ume.ldap.access.user>[email protected]</ume.ldap.access.user>
<ume.ldap.access.server_port>389</ume.ldap.access.server_port>
<ume.ldap.access.base_path.user>OU=Users,OU=Company,DC=company-tst,DC=local</ume.ldap.access.base_path.user>
<ume.ldap.access.password>$ume.ldap.access.additional_password.1</ume.ldap.access.password>
<ume.ldap.access.base_path.grup>OU=Groups,OU=Company,DC=company-tst,DC=local</ume.ldap.access.base_path.grup>
<ume.ldap.access.objectclass.user>User</ume.ldap.access.objectclass.user>
<ume.ldap.access.objectclass.uacc>User</ume.ldap.access.objectclass.uacc>
<ume.ldap.access.objectclass.grup>Group</ume.ldap.access.objectclass.grup>
<ume.ldap.access.naming_attribute.user>cn</ume.ldap.access.naming_attribute.user>
<ume.ldap.access.auxiliary_naming_attribute.user>samaccountname</ume.ldap.access.auxiliary_naming_attribute.user>
<ume.ldap.access.naming_attribute.uacc>cn</ume.ldap.access.naming_attribute.uacc>
<ume.ldap.access.auxiliary_naming_attribute.uacc>samaccountname</ume.ldap.access.auxiliary_naming_attribute.uacc>
<ume.ldap.access.naming_attribute.grup>cn</ume.ldap.access.naming_attribute.grup>
<ume.ldap.unique_user_attribute>samaccountname</ume.ldap.unique_user_attribute>
<ume.ldap.unique_uacc_attribute>samaccountname</ume.ldap.unique_uacc_attribute>
</privateSection>
</dataSource>
</dataSources><?xml version="1.0" encoding="UTF-8" ?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>WebApp</display-name>
- <welcome-file-list>
<welcome-file>login.html</welcome-file>
</welcome-file-list>
- <error-page>
<error-code>404</error-code>
<location>/Error.html</location>
</error-page>
<jsp-config />
</web-app>
This is a very simple war with no component and an error page is defined. But this doesn't work. When I type something like /loginnnn.htmllll, it doesn't give me the error page. That is my problem. Any idea??? -
Live Auction has been installed, but doesn't work
Hi experts!
I've got a lot of errors - LAC doesn't work - Need your help!
1: (SmokeTest):
Make sure the Live Auction initiator's applet JAR file has been properly deployed. This file should be located at H:\usr\sap\SRN\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\com.sap.srm.la\servlet_jsp\srm\root\srm\nullsrmlaInitiator5.10.0.jar.
If you are accessing this page outside of the firewall and via a web dispatcher or reverse proxy, then make sure you can download the JAR file using the "Download" button below. Alternatively, you can try accessing this page inside the firewall to verify that the JAR file is deployed properly.
URL=http://serverzzz.zzz.zz:8002/srm/nullsrmlaInitiator5.10.0.jar
2: Process Bid Invitation -> Action -> Bid Comparison
Error when processing your request
What has happened?
The URL http://serverzzz.zzz.zz:8002/sap/bc/gui/sap/its/BBP_BID_EVAL/! was not called due to an error.
Note
The following error text was processed in the system SRM : Screen output area too small
The error occurred on the application server serverzzz_SRM_zz and in the work process 0 .
The termination type was: ABORT_MESSAGE_STATE
The ABAP call stack was:
SYSTEM-EXIT of program SAPLBBP_BID_EVAL
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SRN in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server serverzzz_SRM_zz in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server serverzzz_SRM_zz . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 100 -u: PURMANAGER -l: E -s: SRN -i: serverzzz.zzz.zz -w: 0 -d: 20081031 -t: 091757 -v: ABORT_MESSAGE_STATE -e: Screen output area too small
HTTP 500 - Internal Server Error
3: Process Auction -> Display Company Bid -> Live Auction
Service cannot be reached
What has happened?
URL http://serverzzz.zzz.zz:8002/sap/bc/gui/sap/its/_accessibility=0 call was terminated because the corresponding service is not available.
Note
The termination occurred in system SRM with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:R-i:serverzzz_SRM_zz-v:0-s:404-r:Notfound
HTTP 404 - Not found
So, first of all as far I understand path to JAR files is misconfigured. Where and how can I fix it?
Any help will be appreciated!
Edited by: Maxim Pak on Oct 31, 2008 4:44 AMI cannot explain it other than to tell you the current recommendations are to keep java turned off and there are no other posts like yours that claim they need it on (at least that I have seen). Also I have it off on my system and flash plays with no problems in all the sites I go to (modulo some buffering problems sometimes with certain hi-res videos on only youtube).
Did you install the latests flash player downloaded directly from the adobe site?
Maybe you have a flash storage or cookie problem. Those can be cleared and deleted with the Flash Player system preferences.
It's your decision on whether you want to take your chances with Java on rather than find the root of the problem. If you do that then at a minimum make sure you have latest apple java updates, I recommend you install and learn about Little Snitch, and use OpenDNS DNS servers (208.67.222.222, 208.67.220.220). -
ABAP WebDynpro work item in uwl doesn't work
Hi,
an ABAP WebDynpro by itself works. But using it in a uwl work item doesn't work:
After clicking the button to start the WebDynpro in a uwl work item a browser opens but the site could not be load.
So something is wrong with the url:
http://<host>:<port>/irj/servlet/prt/portal/prteventname/Navigate/prtroot/pcd!3aportal_content!2fevery_user!2fgeneral!2fdefaultDesktop!2fframeworkPages!2fframeworkpage!2fcom.sap.portal.innerpage!2fcom.sap.portal.contentarea?NavigationTarget=ROLES%3A%2F%2Fportal_content%2Fevery_user%2Fgeneral%2Fuwl%2Fcom.sap.netweaver.bc.uwl.uwlLaunchWebdynproABAP&System=T70CLNT100&WebDynproNamespace=sap&WebDynproApplication=zwps_bspobj_Ship_set&DynamicParameter=wi_id%3D000000004020%26WI_ID%3D000000004020&CurrentWindowId=WID1181552609217&NavMode=1
This is the uwl configuration part:
[code]
<ItemType name="uwl.task.webflow.TS97300003.T70CLNT100" connector="WebFlowConnector"
defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
<ItemTypeCriteria systemId="T70CLNT100" externalType="TS97300003" connector="WebFlowConnector"/>
<Actions>
<Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproABAPLauncher"
returnToDetailViewAllowed="yes" launchInNewWindow="yes"
launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=yes,
menubar=yes,location=yes,directories=yes">
<Properties>
<Property name="WebDynproApplication" value="zwps_bspobj_Ship_set"/>
<Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,
toolbar=yes,menubar=yes,location=yes,directories=yes"/>
<Property name="DynamicParameter" value="WI_ID=${item.externalId}"/>
<Property name="openInNewWindow" value="yes"/>
<Property name="WebDynproNamespace" value="sap"/>
<Property name="display_order_priority" value="5"/>
</Properties>
<Descriptions default=""/>
</Action>
</Actions>
</ItemType>[/code]
What's wrong? Any idea?
Thanks,
SusanneHi,
Your settings seems alright, Can you look at the default trace and UWL log?
U can find UWL log here
\usr\sap\<SID>\JC<instance number>\j2ee\cluster\server0\log\applications\sap.com\uwl
and default trace in \server0\log .. please check the current default trace.
Cheers!!
Ashutosh -
Login/sso doesn't work suddenly
Hello forum,
we have a little problem with our productive PI 7.0. Out of a sudden the login on Repositoy and Directory doesn't work anymore. RWB, ABAP login and SLD work properly. Out admin is on holiday and hopefully hasn't changed anything to our user data... Is there a task or anything which could cause this?
If yes, how to fix it?
Regards
ChristianHI,
You can do soft restart through tcode SMICM on Abap stack.
Tab --> Administration --> ICM --> J2EE Instance --> Send Soft Shutdown --> With Restart.
It will restart only java stack.
Regards,
Anurag -
NameTrans doesn't work in Sun One 7
hi,
OS Solaris 10
Web: Sun One 7u1
this line in obj.conf doesn't work anymore in Sun Web 7, but worked in 6.xx
NameTrans fn="pfx2dir" from="/rabota/css" dir="/opt/semen/secure/rabota-css" name="es-internal"
What changes should be applied for Web 7???
--mpechhi,
yes.
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# You can edit this file, but comments and formatting changes
# might be lost when you use the administration GUI or CLI.
<Object name="default">
AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"
NameTrans fn="ntrans-j2ee" name="j2ee"
NameTrans fn="pfx2dir" from="/mc-icons" dir="/sun/webserver7/lib/icons" name="es-internal"
NameTrans fn="pfx2dir" from="/aaa/images" dir="/sun/webserver7/https-mir/docs/img" name="es-internal"
PathCheck fn="uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index-j2ee"
PathCheck fn="find-index" index-names="index.html,home.html,index.jsp"
ObjectType fn="type-j2ee"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD|POST)" type="*~magnus-internal/*" fn="send-file"
Service method="TRACE" fn="service-trace"
Error fn="error-j2ee"
AddLog fn="flex-log"
</Object>
<Object name="j2ee">
Service fn="service-j2ee" method="*"
</Object>
<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
<Object name="send-precompressed">
PathCheck fn="find-compressed"
</Object>
<Object name="compress-on-demand">
Output fn="insert-filter" filter="http-compression"
</Object> -
Error mapping doesn't work for me. Plz Help!
I have created a .war using deploytool and added "404, /WEB-INF/NoSuchPage.html" in the error mapping area in file refs on the right tabbed panes.
When I deploy the war and test it, the error mapping doesn't work. The server still display the default 404 page to me.
What is the problem?
I do have checked the descriptor. It contains:
<error-page>
������<error-code>404</error-code>
������<location>/WEB-INF/NoSuchPage.html</location>
</error-page>
Any help will be greatly appreciated!<?xml version="1.0" encoding="UTF-8" ?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
<display-name>WebApp</display-name>
- <welcome-file-list>
<welcome-file>login.html</welcome-file>
</welcome-file-list>
- <error-page>
<error-code>404</error-code>
<location>/Error.html</location>
</error-page>
<jsp-config />
</web-app>
This is a very simple war with no component and an error page is defined. But this doesn't work. When I type something like /loginnnn.htmllll, it doesn't give me the error page. That is my problem. Any idea??? -
Web Dynpro dropdown doesn't work for Adobe Reader 8
Hi All,
I've developed a Web Dynpro project which uses Interactive form.
The form has a dropdown (simple type from WDJ).
The dropdown works for Adobe Reader 7 but doesn't work for Adobe Reader 8 (when I press the arrow to open the list nothing happens).
Do I need to config/install something for supporting Adobe Reader 8?
I'm using J2EE 7.13.
Thanks,
OmriDear Omri,
Make sure that you are using Adobe Reader 8.1.1.
Thanks and Regards,
Anto.
Maybe you are looking for
-
Streaming with on2 VP6 8 bit alpha canne
I need to send a live streaming to Adobe Flash Media Server encoded with on2 VP6 8 bit alpha cannel (chroma key) so all clients see only the speaker with no background. what hardware or software support realtime encode VP6 alpha channel ? thanks
-
No need for Xerces jars since Sun includes it in the jvm?
Hey Everybody, If one would like to use Xerces in a java app, why should they download it from Apache when it's included in Sun's jvm releases as of 1.4? I noticed that the "rt.jar" in Sun's jvm for Windows contains an apache folder: jdk1.6.0_11\jre\
-
About to Purchase Macbook Pro, with reservations
I am about to purchase a Macbook Pro, but I have some reservations I wanted to level about, and get the communities opinion. I really want leopard when it is released in October, but I'm going to school, so I cant wait till then to purchase it. I've
-
Retrospect support for the OPTIARC DVD RW AD-7170A
Hi there, Has anyone communicated with EMC re. Retrospect supporting the OPTIARC DVD RW AD-7170A drive on the Mac Pro? I see that others are experiencing issues with the Mac Pro's DVD drive on the Retrospect forum so I thought I'd ask here. Cheers, -
-
Need to Create a Report on 0TCT_C01 as No of Navigations for Queries.
Hi, I have a report Requirement on 0TCT_C01 as Number of Navigations for Queries. already we are activated the Info Cube and loaded the data, now the data is avalible in the Cube. Report like In Column Fields: Validity Period :Query:No of Navigatio