JMS Failover Implementation With Cluster Consist Of Four Servers

Hi All,
I mistankly posted the following thread in a WebLogic general area. It should be here. Can any one help please.
[Document for JMS Failover Implementation On WebLogic|http://forums.oracle.com/forums/thread.jspa?threadID=900391&tstart=15]
Could you please just reply here.
Thanks :)

Similar Messages

Document for JMS Failover Implementation On WebLogic

Hi,
I am looking some good links and techniques to implement JMS failover using WebLogic 10.3.
FailOver* [As we do with our Databases (Concept of Clustring)]
System will consist of two app servers and each will have its own application deployments but if one failed for some reason the application messages should redirected to the other servere and vice versa.
Above efinition is very brief but if anyone can help provide some good documents and info how to implement it it will be appriciated.
Thanks :-)

Thanks alot guys for your help. We successfully implemented it at our servers here by creating distributed queues targetting all servers in a cluster.
One point which I think is worth mentioning and I want to share with all us here is that; when App Server [where MDB will post the message finally after retrieving from queue] if that goes down what will happen, what MDB will do with that message?.
We impleneted the DLQ (error destination) and deploy one more MDB_DLQ_SERVER2 (Let say App SERVER 1 is down) which gets triggered when any message comes to DLQ and post that message to some other App Server, Let say message has been read by MDB_SERVER1 on SERVER1 but offcourse actaull server is down so message should get Re-directed to its Error Destination after it expiration peiod or whatever the settings are. DLQ (Error Destination) which is also a distributed destinatrion again targetting all servers in cluster same as actaull Request or Reply queues BUT MDB_DLQ_SERVER2 which is deployed on Server2 is NOT able to read this message. It get triggered but can not access the message.
After debugging for almost a day we found out its because message has been transafed to DLQ but actaully its resides in a FILESTORE_SERVER1 and MDB_DLQ_SERVER2 is not able to access it.
To work with that we have to define MDB_DLQ_SERVER1 to cater the SERVER1 failure and MDB_DLQ_SERVER2 to cater SERVER2 failure.
Reason I am mentioning this because as I said DLQ is also a normal Distributed Queue but at the same time its NOT as Distributed as its says.
Hope you all understand what I just wrote above.
Now I need to implement exactly the same scenario using four seperate physicall machine containing my four servers. I tried this scenario by creating four machines where node manager for each server is running and listning but when I am trying to start the server it gives me Certificate Exception with bad user name and password. Anyway I have seen some posts here regarding this; So i think i'll be fine.
Thanks Again,
Sheeraz

JMS Failover with Distributed Destinations in 7.0

          How does JMS failover with distributed destinations in WL 7.0?
          In an environment using file stores for persistent messages, can a working server
          automatically pick up unprocessed and persisted messages from a failed server?
          If so, what's the best way to set this up?
          Or, is this completely manual? In other words, we have to bring up a new server
          pointing to the location of the file store from the failed server?


          It appears that two JMSServers cannot share the same file store and, I'm assuming,
          two file stores cannot be using the same directory for persistence.
          So the HA you're talking about is something like Veritas automatically restarting
          a server (or starting a new one) to process the messages in the persistent queue
          that were unprocessed at the time of failure with the file store residing on some
          sort of HA disk array.
          The key point is that a message once it arrives at a server must be processed
          by that server or, in the case of failure of that server, must be processed by
          a server similarly configured to the one that failed so that it picks up the unprocessed
          messages. The message can't be processed by another server in the cluster.
          Or, is there some trick that could be employed to copy from the file store of
          the failed server and repost the messages to the still operating servers?
          "Zach" <[email protected]> wrote:
          >Unless you have some sort of HA framework/hardware, this is a manual
          >operation. You either point to the existing persistent storage (shared
          >storage or JDBC connection pool), or you move the physical data.
          >
          >_sjz.
          >
          >"Jim Cross" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >>
          >> How does JMS failover with distributed destinations in WL 7.0?
          >>
          >> In an environment using file stores for persistent messages, can a
          >working
          >server
          >> automatically pick up unprocessed and persisted messages from a failed
          >server?
          >> If so, what's the best way to set this up?
          >>
          >> Or, is this completely manual? In other words, we have to bring up
          >a new
          >server
          >> pointing to the location of the file store from the failed server?
          >
          >

JMS Failover & Load balancing.

Hi,
I have 4 Managed servers A,B,C,D on 4 physical boxes. We have one JMs server on Box D, All other Managed server uses this only JMS which is on D, if this goes down we loose all messages. I want to have JMS failover in my environment. I suggested to have 4 JMS servers and 4 File stores for each Managed server? my question is that Is weblogic that intellegent that if a client connects to box B JMS server and if the servers goes down, the message will be send top another JMS server?

ravi tiwari wrote:
Hi,
I have 4 Managed servers A,B,C,D on 4 physical boxes. We have one JMs server on Box D, All other Managed server uses this only JMS which is on D, if this goes down we loose all messages. I want to have JMS failover in my environment. I suggested to have 4 JMS servers and 4 File stores for each Managed server? my question is that Is weblogic that intellegent that if a client connects to box B JMS server and if the servers goes down, the message will be send top another JMS server?You don't mention if you're running in a clustered environment or what
version of WLS you're using, so I've assumed a cluster and WLS 8.1
For resiliency, you should really have 4 JMS servers, one on each
managed server. Then each JMS server has it's own filestore on the
physical managed server machine.
So, you have JMSA, JMSB, JMSC, JMSD with FileStoreA, FileStoreB,
FileStoreC & FileStoreD.
You should also look at using JMS distributed destinations as described
in the documentation.
In your current environment, if server D goes down, you not only lose
your messages, your application would lose access to your JMS queues?
If you use distributed destinations, and have 4 JMS servers, your JMS
queues will still be available if a single server goes down.
If a server does go down however, you have to follow the JMS migration
procedures to migrate the JMS service from the failed server to a
running one.
There are conditions to this process, which are best found out from the
migration documentation to be honest, rather than describe it here.
We use this setup, and it works fine for us. We've never had to use JMS
migration, as so far we haven't had anything serious to cause us to need
to migrate. Our servers also boot from a SAN which makes our resilience
processes simpler.
Hope that helps,
Pete

JMS failover

          We have an external EDI service posting XML data over http to Weblogic JMS server,
          we have 2 physical machines which run the weblogic and JMS, our EDI can only feed
          to one server so if that server goes down what would be the best way to automactically
          failover to the other Weblogic JMS, since JMS server cannot be clustered.We are
          infact using a database based queue.
          Thanks
          Anil Jacob


          Hi Anil,
          you are correct that automatic migration is not supported in weblogic server so
          you will need to take care of this yourself.
          We have written a little java program that runs of the same server that our admin
          server is running on. This program has two purposes, one is to restart the admin
          server incase it should goes down. This is because the we need to trigger the
          migration through the admin server. The second is to poll the managed servers
          and and migrate when needed.
          The methods that handle the migration are located in weblogic.management.runtime.MigratableServiceCoordinatorRuntimeMBean.
          So as an example you could get a referense to this mbean by writing:
          MBeanHome home = Helper.getMBeanHome(wls_user, wls_password, admin_url, admin_server_name);
          MigratableServiceCoordinatorRuntime mrt = home.getRuntimeMBean("the-MigratableServiceCoordinator",
          "MigratableServiceCoordinatorRuntime");
          mrt.migrate(migratableTargetMBean, destinationServer, false, true);
          We are using bea`s types interfaces for this but you can also use "pure" jmx calls,
          but I was is a hurry and this seemed to be quicker.
          Below is the javadoc for the migrate method that bea`s support provided us.
          * Migrate all services deployed to the migratableTarget to the destination
          * server. Use this method if either the source or the destation or both are
          * not running.
          * Precondition:
          * The migratableTarget must contain at least one server.
          * The destination server must be a member of the migratableTarget's list
          of
          * candidate servers.
          * If automatic migration mode is disabled, the destination server must not
          * be the currently hosting server (i.e. head of candidate list of the
          * migratableTarget).
          * Postcondition:
          * If automatic migration mode is disabled and if the migration succeeded,
          * the head of the candidate server list in the migratableTarget will be the
          * destination server.
          * @param migratableTarget - all services targeted to this target are to be
          * migrated to the destination server.
          * THIS MUST BE A CONFIG MBEAN
          * @param destination - the new server where the services deployed to
          * migratableTarget shall be activated
          * @param sourceUp - the currently active server is up and running. If false,
          * the administrator must ensure that the services deployed
          * to migratableTarget are NOT active.
          * @param destinationUp - the destination server is up and running.
          void migrate(MigratableTargetMBean migratableTarget, ServerMBean destination,
          boolean sourceUp, boolean destinationUp) throws MigrationException;
          If you take a look at the weblogic.management.configuration.MigratableTargetMBean
          it has a method named getHostingServer(). This method returns a ServerMBean which
          tells us on which server the jms services are bound. This the same as the "CurrentServer"
          in the admin console. These objects have names like "appserver1 (migratable)"(where
          appserver1 would be replaced with the name of your managed server). This can
          be abit confusing if you look at the admin server log would can somtime see that
          is is migrating "appserver1 (migratable) to appserver1", which migth look stange(well
          it did for me:)). Just remember that "appserver1 (migratable)" is just the name
          of the migratable target, and that object has the "CurrentServer" attribute .
          The "CurrentServer" is the server where the services are right now, and it is
          that server that we are migrating the services from.
          I think that your ide of have inte a backup jms server running of a second wls
          will work just fine. You should be able to poll the server which is hosting the
          jms service, and if it goes down you migrate the migratable target to the second
          server. You could stop there and manually "reset" the configuration to your
          starting state or fully automate so that the second server takes over and the
          first becomes you back up.
          Just ask if some of this isn`t very clear.
          /Daniel
          "Anil Jacob" <[email protected]> wrote:
          >
          >Daniel,
          >
          >That was a pretty good explanation. Thanks. Our application vendor does
          >not support
          >distributed queues therefore right now that option might not be used
          >in our case,
          >however the migratable option for JMS that you discribed looks good.
          >Is migration
          >an automactic process, I don't think so, what do you say?
          >What I want to acheive given the limited options is to have a backup
          >Weblogic
          >JMS which would come alive once the primary goes down, in this case your
          >idea
          >of a script looks good, can you give me more details on the script that
          >polls
          >the managed server and migrates JMS incase of a failure?
          >
          >Thankx
          >Anil
          >
          >[email protected] (Daniel Bevenius) wrote:
          >>Hi,
          >>
          >>What you could do is have a distributed destination as the previous
          >>post suggested. This distributed destination could then have one
          >>member that is pinned to a JMS server on one of you`re managed
          >>servers. This JMSServer should have its target set to appserver1
          >>(migratable).
          >>
          >>
          >>In you`re case you say that you can only target one server with the
          >>EDI feed which means that you will need to manually migrate the jms
          >>services to the second server.
          >>
          >>We had to create a program that polls the servers to see if they are
          >>alive. If one goes down we migrate the jms services automatically to
          >>the server that is still up.
          >>
          >>You stated that JMS servers could not be clustered. In our setup we
          >>have a JMSServer on each managedserver(we have two in a cluster).
          >>According to BEA support the problem with automatic failover is with
          >>consumers that bind to a distributed destination(note that this is not
          >>so for producers).
          >>When a client binds to a distributed destination it will get a binding
          >>to one of the members of that distributed destinaion, which depends
          >on
          >>the load balancing policy(we use round robin). Lets say that the
          >>client binds to a jms server on our first managedserver. If this
          >>server crashes the the client will still have a binding to the first
          >>managed server. What we are migrating is the binding to a different
          >>jms server.
          >>
          >>Don`t know if this helps you at all but let me know and I`ll try to
          >>explain it better.
          >>
          >>/Daniel
          >>
          >>
          >>
          >>
          >>"Anil Jacob" <[email protected]> wrote in message news:<[email protected]>...
          >>> We have an external EDI service posting XML data over http to Weblogic
          >>JMS server,
          >>> we have 2 physical machines which run the weblogic and JMS, our EDI
          >>can only feed
          >>> to one server so if that server goes down what would be the best way
          >>to automactically
          >>> failover to the other Weblogic JMS, since JMS server cannot be clustered.We
          >>are
          >>> infact using a database based queue.
          >>>
          >>> Thanks
          >>> Anil Jacob
          >

JMS Server deployed to cluster of servers

Hey guys,
I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
I read the following passage in the weblogic documents:
Obtain a Clustered JMS Licence
In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
If i'm just building a model does this apply to me?
Thanks

continued reading to clarify. Problem solved, thanks for looking

What is the best way to implement a cluster-wide object ID generator?

What is the best way to implement a cluster-wide object ID generator?

What is the best way to implement a cluster-wide
object ID generator?Always use 3 because it is prime.
Alternatively more information about the system and the needs of the system might prompt alternative ideas some of which are likely to be better than others for your particular implementation and system constraints.

How to know if implementation with a filter value exist for a BAdI in code?

Hi all,
Scenario:
I created a BAdI. There will be a button on the UI to call its implementation(s); while if there is no implementation with specified filter value, this button needs to be hidden. Thus I need to know if the implementation exist before calling it.
Question:
In the ABAP code, how to get whether implementation with specified filter value exists for a BAdI?
If it's possible, please help provide code.
Thanks and regards,
Said

Problem solved:
data: r_badi type ref to YOUR_BADI,
          badi_impl_num type i.
get badi r_badi
    filters
      flt_name = fit_val.
badi_impl_num = cl_badi_query=>number_of_implementations( badi = r_badi ).
if badi_impl_num > 0.
    "there are badi implementation(s)
endif.

CRS-4535: Cannot communicate with Cluster Ready Services

[oracle@bnl11237dat01 ~]$ /u01/app/11.2.0/grid/bin/cluvfy stage -post crsinst -n bnl11237dat01,bnl11237dat02 -verbose
Performing post-checks for cluster services setup
Checking node reachability...
Check: Node reachability from node "bnl11237dat01"
Destination Node Reachable?
bnl11237dat01 yes
bnl11237dat02 yes
Result: Node reachability check passed from node "bnl11237dat01"
Checking user equivalence...
Check: User equivalence for user "oracle"
Node Name Comment
bnl11237dat02 passed
bnl11237dat01 passed
Result: User equivalence check passed for user "oracle"
ERROR:
Unable to obtain network interface list from Oracle Clusterware (OIFCFG)
Verification cannot proceed
Post-check for cluster services setup was unsuccessful on all the nodes.
[oracle@bnl11237dat01 ~]$ oifcfg iflist
bond1 10.32.25.160
bond2 10.32.17.200
bond2 169.254.0.0
bond0.1515 10.32.24.0
bond0.1536 172.16.7.0
[oracle@bnl11237dat01 ~]$ oifcfg iflist -p
bond1 10.32.25.160 PRIVATE
bond2 10.32.17.200 PRIVATE
bond2 169.254.0.0 UNKNOWN
bond0.1515 10.32.24.0 PRIVATE
bond0.1536 172.16.7.0 PRIVATE
[oracle@bnl11237dat01 ~]$ oifcfg iflist -p -n
bond1 10.32.25.160 PRIVATE 255.255.255.240
bond2 10.32.17.200 PRIVATE 255.255.255.248
bond2 169.254.0.0 UNKNOWN 255.255.0.0
bond0.1515 10.32.24.0 PRIVATE 255.255.255.192
bond0.1536 172.16.7.0 PRIVATE 255.255.255.0
[oracle@bnl11237dat01 ~]$ /u01/app/11.2.0/grid/bin/onsctl debug
HTTP/1.1 200 OK
Content-Length: 1923
Content-Type: text/html
Response:
== bnl11237dat01:6200 8732 11/05/19 11:44:09 ==
Home: /u01/app/11.2.0/grid
======== ONS ========
IP ADDRESS PORT TIME SEQUENCE FLAGS
127.0.0.1 6200 4dd4f2a3 00000000 00000008
Listener:
TYPE BIND ADDRESS PORT SOCKET
Local 127.0.0.1 6100 5
Remote any 6200 7
Remote any 6200 -
Connection Topology: (1)
IP PORT VERS TIME
127.0.0.1 6200 4 4dd4f2a3=
Client connections:
ID CONNECTION ADDRESS PORT FLAGS SENDQ REF SUB W
0 internal 0 01008a 00000 001 002
2 127.0.0.1 6100 01001a 00000 001 001
1 127.0.0.1 6100 01001a 00000 001 001
3 127.0.0.1 6100 01001a 00000 001 001
4 127.0.0.1 6100 01001a 00000 001 001
7 127.0.0.1 6100 01001a 00000 001 000
request 127.0.0.1 6100 03201a 00000 001 000
Worker Ticket: 10/10, Last: 11/05/19 11:42:21
THREAD FLAGS
40460940 00000012
405b4940 00000012
41280940 00000012
Resources:
Notifications:
Received: Total 0 (Internal 0), in Receive Q: 0
Processed: Total 0, in Process Q: 0
Pool Counts:
Message: 1, Link: 1, Ack: 1, Match: 1
[oracle@bnl11237dat01 ~]$
[root@bnl11237dat01 ~]# /u01/app/11.2.0/grid/bin/crsctl stop crs
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.crsd' on 'bnl11237dat01'
CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.bnl11237dat01.vip' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.oc4j' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.cvu' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN3.lsnr' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.bnl11237dat01.vip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.cvu' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.scan1.vip' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.bnl11237dat02.vip' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.LISTENER_SCAN3.lsnr' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.scan3.vip' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.LISTENER_SCAN2.lsnr' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.scan2.vip' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.scan1.vip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.bnl11237dat02.vip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.scan3.vip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.scan2.vip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.oc4j' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.ons' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.ons' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.net1.network' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.net1.network' on 'bnl11237dat01' succeeded
CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'bnl11237dat01' has completed
CRS-2677: Stop of 'ora.crsd' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.mdnsd' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.crf' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.ctssd' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.evmd' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.mdnsd' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.crf' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.evmd' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.ctssd' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.cssd' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.gipcd' on 'bnl11237dat01'
CRS-2673: Attempting to stop 'ora.diskmon' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.gipcd' on 'bnl11237dat01' succeeded
CRS-2673: Attempting to stop 'ora.gpnpd' on 'bnl11237dat01'
CRS-2677: Stop of 'ora.diskmon' on 'bnl11237dat01' succeeded
CRS-2677: Stop of 'ora.gpnpd' on 'bnl11237dat01' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'bnl11237dat01' has completed
CRS-4133: Oracle High Availability Services has been stopped.
[root@bnl11237dat01 ~]# /u01/app/11.2.0/grid/bin/crsctl start crs
CRS-4123: Oracle High Availability Services has been started.
[root@bnl11237dat01 ~]# /u01/app/11.2.0/grid/bin/crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4534: Cannot communicate with Event Manager
I am unable to start Oracle Cluster Service on 11.2.0.2. Please can I know what the problem is and how to start CRS
thanks.

Hi,
after the crsctl start crs you have to wait a while till the clusterstack is up. You just issued crsctl check crs a little to early.
To see the startup stack do a crsctl stat res -t -init.
If not everything in crsctl stat res -t -init goes to online after a while, then you have a problem, which has to be analyzed.
However if crsctl stat res -t -init show everything is started use crsctl stat res -t to see the other processes coming online.
Can you post the crsctl stat res -t -init (if not everything is online) or a crsctl stat res -t.
Only thing which I find strange is that oifcfg does not list a PUBLIC interface...
Regards
Sebastian

Can access enforcer be implemented with going through the SOD check.

Hi All,
I have couple of questions regarding Access enforcer:
1. Can Access enforcer be implemented with going through the SOD check?
2. Can we provision roles for the project team using Access Enforcer (without having a million SOD conflicts which need to be cleared)?
I would really appreciate any insight on these questions.
Thanks

https://websmp103.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000015092&_HIER_KEY=601100035870000206624&_HIER_KEY=601100035870000212731&_HIER_KEY=601100035870000210510&_HIER_KEY=701100035871000519581&_SCENARIO=01100035870000000202&#HOME

SAP Security Planning and implementation with SOX/SOD compliance

hello
Hi guys, i am a security guy
could you tell me ,"SAP Security Planning and implementation with SOX/SOD compliance"
what does it mean.
<removed_by_moderator>
thanks
Ramesh
Edited by: Julius Bussche on Feb 2, 2008 1:26 PM

Ramesh Sammiti wrote:>
> hello
>
> Hi guys, i am a security guy
>
> could you tell me ,"SAP Security Planning and implementation with SOX/SOD compliance"
>
> what does it mean.
>
>
> <removed_by_moderator>
>
>
> thanks
> Ramesh
Forgive me for saying, but it means:
Implementing security which complies with Sarbanes Oxley requirements and takes into account Segregation of Duties.
SOX and SOD are different things, from a security perspective SOX is generally technical security based and SOD is business process based (although bus proc has big SOX component).
There is a plethora of information via yahoo/google etc.
Edited by: Julius Bussche on Feb 2, 2008 1:28 PM

WSDL with messages consisting of multiple parts

Hi,
I need to create an ABAP client for a Web Service. In the WSDL of the Service I want to call, there are messages consisting of multiple parts like this one:
     <message name="AddOrUpdateSeekersIn">
              <part name="header" element="mh:MonsterHeader"/>
               <part name="catheader" element="cat:CompanyAuthHeader"/>
             <part name="body" element="monster:JobSeekers"/>
     </message>
I've found a document that says this is not supported by the ABAP Proxy Generation wizard.
On the ABAP forum (WS Proxy Generation for WSDL with messages consisting of multiple parts) someone suggested me to ask for advice here on whether I would modify the WSDL so that the message only contains one part. Is this possible and how would I do that?
Thanks,
Tim

Have u ever know the agile way of building messages for SERVICE by reusing data types in XSDS?
When ever u define a Service and Service Operation you have to define Request, Response, Fault messages for EACH Service operation.
A message is not always same as DATA, however a message is the DATA representation in a SERVICE operation context to address the operation Request, Response and FAULT (Exception)
Always try to build the message requirement of a service operation in such a way so that we can reuse the data types.
So during the service requirement analysis, decompose all DATA REKS such a way so that we can build data entities as
atomic data types
composite data types and
canonical data types in a such a way
atomic data types are part of composite data types
and composite data types are part of canonical data types
and canonical data types map to business service operation request and response
composite or atomic data types map to FAULT messages
This way you will have an agile approach to fullfill the data requirement of messages in services context, also can avoid the technology limitation in service enabled platform such as ABAP R3
PS: there might be a other temp solution, but this should be the way we do in SOA practice.
Thanks

Can be implemented with Java 2D?

Could anyone tell me what kind of effect in this flash animation? it can be implemented with Java 2D?
http://www.echt-wahnsinn.de/liebesgesichtflash.htm

Thanks for your answer.
so it's not only just for fun but the part of our semester project. :-)
Could you explian it more in detail, I mean "manipulate the color/brightness values"
please tell me if the step is right:
1. load a new image as background pic and another new pic as the small image (using BufferedImage)
because I will scale(maybe scale = 0.5) the both pics in my UI window.
. img_org . img_min . img_result .
2. create the background pic in third ImagePanel automatically and finish the image manipulations.
at the same time to get the size of img_org, img_min, and color/brightness values, pixels.
here I am not sure how to implement it effectively. image clipping?
any suggestion and help are welcome!!
laue

Have any companies setup a domain with cluster using BEA platform8.1 sp2?

Hi, everyone,
Do you know who has setup a domain with cluster in production using BEA platform8.1 sp2. That is, the customer uses portal and integration in the same managed server, and uses the cluster technique.
I want to know whether there was a successful case or not till now. If possible, please send me some information about it. My account is [email protected], or [email protected]
Thank you very much.
Loen xie

Hi, everyone,
Do you know who has setup a domain with cluster in production using BEA platform8.1 sp2. That is, the customer uses portal and integration in the same managed server, and uses the cluster technique.
I want to know whether there was a successful case or not till now. If possible, please send me some information about it. My account is [email protected], or [email protected].
Thank you very much.
Loen xie

Where can I get the patch for Oracle JMS to work with RDBMS 9.2.0.1

Hi,
In the following extract from Oracle documentation the patch is mentioned that needs to be applied.
"You must apply a server-side patch for Oracle JMS, which ships with Oracle9iAS Release 2 (9.0.3) and the OTN release of OC4J, to work with an RDBMS 9.2.0.1 database. This patch is documented as bug 2513629; see the Metalink Web site or contact Oracle support for more information. However, it is strongly recommended that users move to RDBMS 9.2.0.2 when it is available. Users do not need to apply any server-side database patches when running with RDBMS 9.2.0.2."
Where I can get this patch?
Is it RDBMS patch or OC4J patch?
I don't have access to a Metalink.
Thanks a lot,
Andrei

Check out the configuration on the mapping. There you can create a data file. Do that and fill out the other parameters for the bad and discard file in that node.
Jean-Pierre

JMS Failover Implementation With Cluster Consist Of Four Servers

Similar Messages

Maybe you are looking for