Replication scenario

Hello,
I would like to use the following replication model :
5 servers. Each in write mode. So all have to be master configured
<---> : multi-replication
-----> : one way replication
M1 <--> M2
M3 <--> M4
M1 ----> M3
M1 ----> M4
M2 ----> M3
M2 ----> M4
M3 ----> M5
M4 ----> M5
Is it a possible configuration ?

Current version of the directory server (5.2P4) does not support more than 4 masters. If you omit M5 (perhaps you can make it a consumer), then all the other combinations are possible. This is btw called a fully meshed configuration. You actaully don't need to have a full mesh in order to provide fail over but nevertheless it is entirely legal.
Regards,
-Wajih

Similar Messages

Unit 4 Assignment 1, AD Replication Scenario

what is the recommendations for site-link protocols and replication schedule/frequency as well as the possibility of recommending/justifying redundant links to branch 1 ?

I have already answered that here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a0507a50-8e4d-48ab-be8f-1f0bfb401f4a/ad-design-replication-scenario?forum=winserverDS#a0507a50-8e4d-48ab-be8f-1f0bfb401f4a
Please note that a DC can remain unreachable for a period that should not be longer than your tombstone lifetime period: https://technet.microsoft.com/en-us/library/cc784932%28v=ws.10%29.aspx
For redundant links, it depends of your requirements, impacts when a site is disconnected and your SLAs. So, I would recommend first to identify your requirements before looking to how the configuration should be.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

I i want to run many-to-one replication scenario

Hi,
i want to run many-to-one replication scenario and for that i have created two tables and inserted values on source db and one table on target db in which i want consolidated data from those two tables. Below are the table details,
Source DB,
CREATE TABLE GGS.CLIENT_INFO
( CLIENT_ID varchar2(10) not null,
CLIENT_NAME varchar2(50) not null,
CLIENT_ADD varchar2(50),
CONSTRAINT CLIENTID_PK PRIMARY KEY (CLIENT_ID)
CREATE TABLE GGS.ACCOUNT_INFO
( ACCOUNT_NO varchar2(15) not null,
BANK_NAME varchar2(50) not null,
CLIENT_ID varchar2(10) not null,
CONSTRAINT ACCTNO_PK PRIMARY KEY (ACCOUNT_NO)
alter table GGS.ACCOUNT_INFO add CONSTRAINT FK_CLIENTINFO FOREIGN KEY (CLIENT_ID) REFERENCES GGS.CLIENT_INFO(CLIENT_ID);
Target DB,
CREATE TABLE GGS1.CLIENT_ACCOUNT_INFO
( CLIENT_ID varchar2(10) not null,
ACCOUNT_NO varchar2(15) not null,
CLIENT_NAME varchar2(50) not null,
CLIENT_ADD varchar2(50),
BANK_NAME varchar2(50) not null,
CONSTRAINT CLIENT_ACCOUNT_PK PRIMARY KEY (CLIENT_ID, ACCOUNT_NO)
when i start replicat process, it is giving below error,
*"Oracle GoldenGate Delivery for Oracle, CLACTDEL.prm: OCI Error ORA-01400: cannot insert NULL into ("GGS1"."CLIENT_ACCOUNT_INFO"."CLIENT_NAME") (status = 1400), SQL <INSERT INTO "GGS1"."CLIENT_ACCOUNT_INFO" ("CLIENT_ID","ACCOUNT_NO") VALUES (:a0,:a1)>."*
Note: i am inserting two source tables data in one table which at target side using OGG capture-replicate process.
Please help to resolve above error.
Regards,
Shital

For one, do not use the GoldenGate database user as your source and target schema owner. Why? What happens in a bidirectional setup? To prevent ping-ponging of data, operations performed by the replicat user should be ignored. That's what keeps the applied update on a target being re-applied on the original source, and then being captured and sent to the target, etc.
Without knowing your setup, what did you do for ADD TRANDATA and supplemental logging at the database level (only needed for the source)? What did you do for initial load and synchronization? What are your parameter files?
The error shown so far - cannot insert null - applies everywhere in Oracle whenever you try to insert a record with a null value in a column where a NOT NULL constraint is present. You can see that for yourself in a SQL*Plus session and trying the insert. You are inserting two column values, when your own table definition shows you would need at least 4 values (to account for all of the not null constraints).

Is schema replicated in multimaster replication scenario?

hellos
I am asking basic question. I have set up a multimaster replication (ids5.1sp2) on database c=fi.. this works well.
however, in the future I know that more objectClasses and attributes will be added to the schema.
My simple question.. is do I have to amend the 99user.ldif files on BOTH ids5.1 servers or can I rely on the schema being replicated.
thanks.

Schema is supposed to replicate in all replication scenario's
The documentation states
"The best way to guarantee schema consistency is to make schema modifications on a single master server, even in the case of a multi-master replication environment.
Schema replication happens automatically. If replication has been configured between a supplier and a consumer, schema replication will happen by default."
However a few people in this forum have complained that this replication doesn't always work - so be sure to check to make sure the schema does in fact replicate.
For more information on schema replication check out this link:
http://docs.sun.com/source/816-5609-10/rep.htm#1063947
It is at the bottom of the page ...

401 - Unauthorized error in Value Mapping Replication scenario

Hi,
I'm trying to push some Value Mapping replication data from one of the clients (which is a non-Integration Server) of XI system to IS. When I execute the program which calls the outbound proxy, the XI message fails with the error HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorised.
As given in SAP help, I registered the inbound java proxies and generated the outbound proxies. I confiured the receiver channel with path /MessagingSystem/receive/JPR/XI. In authentication data, I tried several users such as XISUPER, XIAPPLUSER, XIISUSER..Still I get the same error.
What is missing/wrong?
Thanks in advance
Praveen Sirupa

Hi Praveen,
Could you pls do the following...just for verification....
enter the url http://<was_server>:5<sysnr>00/MessagingSystem/receive/JPR/XI
and when it asks for authentication give the XIAPPLUSER and password...you should get an xml that looks like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <scenario>
<scenname>MSG_SCEN</scenname>
<scentype>SERV</scentype>
<sceninst>MSG_001</sceninst>
<scenversion>001</scenversion>
- <component>
<compname>SERVLET</compname>
<compdesc>Messaging System</compdesc>
<comphost>localhost</comphost>
<compinst>MSG_001</compinst>
- <message>
<messalert>OKAY</messalert>
<messseverity>100</messseverity>
<messarea>QR</messarea>
<messnumber>801</messnumber>
<messparameter>na</messparameter>
<messtext>MessagingServlet is active.</messtext>
</message>
</component>
</scenario>
Thanks,
Renjith

1:N Replication Scenario Approach

Hi,
We plan to split HANA and like to consider the parallel run option whereby we build the new hardware and do a migration/restore from existing Production onto the new box. Then we like to switch on SLT for both the existing and new HANA boxes and run the models in parallel to compare the results before we switch off the old one.
This would mean that we need to setup new SLT triggers for the new server whilst the existing triggers are still running.The current configuration for SLT -- Allow Multiple Usage is not selected.How we can perform this in our landscape?What would be the best approach?

Hi Roy,
look at this note. it describes how to setup 1:n once you already created the config without "multiple usage" flagged.
Best,
Tobias
SAP Note 1898479:
SLT replication: Redefinition of existing DB triggers

Error in Value Mapping Replication scenario

Hello all,
We have developed the scenario to upload the mass data to VMR and which is actually working as expected in Dev environment,
But it is not working in quality after transport.
Also we have regeister the service in JAVA proxy but still facing the issue.
The message is failing in adapter enigne with status system error with the below error :
09.05.2014 10:39:36.435
Information
Trying to retry the message because of administrative action of user
"XVEREKAN".
09.05.2014 10:39:36.437
Information
Admin
action: Trying to redeliver message.
09.05.2014 10:39:36.456
Information
The
message status was set to TBDL.
09.05.2014 10:39:36.465
Information
Retrying
to deliver message to the application. Retry: 4
09.05.2014 10:39:36.465
Information
The
message was successfully retrieved from the receive queue.
09.05.2014 10:39:36.472
Information
The
message status was set to DLNG.
09.05.2014 10:39:36.498
Information
Java
Proxy Runtime (JPR) accepted the message.
09.05.2014 10:39:36.896
Error
JPR
could not process the message. Reason: No such method ValueMappingReplication in
proxy bean
localejbs/sap.com/com.sap.xi.services/ValueMappingApplication.
09.05.2014 10:39:36.897
Error
Delivering the message to the application using connection JPR failed,
due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error processing inbound message. Exception: No such method
ValueMappingReplication in proxy bean
localejbs/sap.com/com.sap.xi.services/ValueMappingApplication.
09.05.2014 10:39:36.905
Error
The
message status was set to NDLV.
Can some one please help on this ?
Thanks.

Hi Amit,
I tried that also but the same error :
Delivering the message to the application using
connection JPR failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error
processing inbound message. Exception: No such method ValueMappingReplication in
proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication.
De-Register the interface using the link :
http://server:port/ProxyServer/unregister?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=ValueMappingReplication
Register :
http://server:port/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=ValueMappingReplication
Result
Interface http://sap.com/xi/XI/System#ValueMappingReplication registered with
value
localejbs/sap.com/com.sap.xi.services/ValueMappingApplication:ValueMappingReplication
My Final Payload after mapping
<?xml version="1.0" encoding="UTF-8"
?>
- <ns1:ValueMappingReplication xmlns:ns1="http://sap.com/xi/XI/System">
- <Item>
<Operation>Insert</Operation>
<GroupID>31322371194085293873227252571012</GroupID>
<Context>http://sap.com/xi/XI</Context>
<Identifier scheme="Source1" agency="Excel">786123test</Identifier>
</Item>
</ns1:ValueMappingReplication>
Thanks,
Anant

Replication scenario (please answer)

We have 96 table in one oracle User and we want to replicate them in bidirectional way, 4-5 tables use for logging and we don't want to replicate them.
which scenario do you suggest to me:
1- Use schema base capture,apply and prevent logging tables to replicate with rule and Tag ?
If yes please tell me how can I restrict some tables in schema to don't replicate.
2- Use table base capture,apply and write it for all necessary table (HUGE work for about 90 tables :( ).
I prefer first one but I don't know how to exclude some tables from schema to don't capture and/or apply.

Do a table level capture and schema level Prop and Apply. That way you filter out the tables in capture level itself and you avoid the second filter again in Prop and Apply level.

Unique identifier in multi-master replication scenario.

Hi,
I am trying to workout whether or not to use nsuniqueid as the unique identifier to pull data out of multi-master replication sun one directory server environment. From another forum I noticed that nsuniqueid can change if the tree structure changes. Is there any unique identifier that I can use which will guarantee that in every master server this unique identifier field will have the same value for the same object? I know that this is not the case for entryid values, as they are assigned different values in different master server.
Thank you in advance,
Johan

Well, depending on your DIT, the usual thing to do is to use some collection of naming attributes, typically the RDN. If all else fails each DN will certainly identify each entry. You should avoid using nsuniqueid for anything in your application logic, though it is certainly unique and identical across the topology for each entry. What nsuniqueid allows you to do that other attributes don't is to differentiate two entries that are otherwise identical, but which have been added at different times. So, for instance, if you added an entry, deleted it, then readded it, the nsuniqueids would be different.
Just make sure you don't do anything silly like putting nsuniqueid in an LDIF template. Always let the server create the nsuniqueid. And when you create a replica initialization LDIF, don't change the nsuniqueids in it.

Replication scenario in 5.2

I'm currently upgrading a series of legacy Netscape 4.x ldap servers at our site. The old architecture is split between a WAN (public IP space) and LAN (10.x.x.x IP space) networks with the Master being on the WAN and various read-only replicas on the LAN. This works in 4.x due to the supported "pull" type replication agreement where the client initiates contact with the Master. Since the Master is in public IP space and a portion of the client read-only replicas are behind a firewall in a LAN, the Master cannot initiate a tcp connection with them, only vice-versa.
Unless I am mistaken, from reading the 5.2 documentation I see that this form of replication is no longer supported, with Master initiated replication being the only option. Is this indeed the case?
thanks,
-jm

Yes, master initiated replication is the only option with the 5.x directory.

Replication issue in ABAP to ABAP scenario

Hello,
I have a ABAP to ABAP replication scenario where I am replicating custom and standard tables like MDMA but found below issue.
The replication current action is struck in "Replication (Initial Load)" with Initial load is getting done but not replicating data afterwards.
Also, the tables is keep on switching between "Failed" and "In process" status. I checked the system is sufficient number of jobs.
I found below error message after checking the show error log.
I restarted the replication many times and even created the configuration but no luck.
Please enlighten me to fix this issue...
Regards

Hi Tobi,
I removed all the records from target table and replicated again but same result.
Initial load is getting done but not replicating data afterwards. And the table is keep on switching between "Failed" and "In process" status.
Regards

Oracle 8i to MS SQL Server replication

Im new to Oracle, but a MS SQL Server DBA. Im helping in the architecture of a data warehouse that pulls from some disparate sources, including Oracle 8i, into a SQL Server 2000 box. We could use batch processing to pull updated data from the Oracle database to populate our data warehouse, but we were hoping to get real-time transactional processing via some replication scenario. My terminology may be wrong from the Oracle perspective, but I think the transactional replication that SQL Server supports is called synchronous replication in Oracle. My question is, does anybody know how to do synchronous replication from an Oracle server to a SQL Server? Or perhaps which Oracle product supports it? Thanks!
null

===========================================================
I'm working on the similar requirements, exactly my source DB is DB2, and the target DB is Oracle. I have two year experience with Oracle, but I know nothing about DB2. There a about 50 tables in source DB. Transactions on source DB is not too heavy(less than 10/Second), and the mainfram are all powerful.
I've though about Oracle Gateway, but I'd rather save it as the backup solution. For one thing, neither co-workers nor I have experience with it. Second, I'm afraid the Gateway performance would not be satisfactory. Furthermore, words has it that we should pay for the Gateway. So My ideas to real-time replication of the two DB is as following:
(1) use trigger in DB2 to reponse to immediate transactions in source DB;
(2) use Embedded C/SQL to extract those transactions into flat files;
(3) FTP files to the target server;
(4) On target server, SHELL scripts read the files and call Pro*C to apply the transactions into Oracle DB.
but, some problems really get me.
A: in step(1) and (2), How to set EC to do its work in reponse to trigger? I know that one can call host script in Oracle trigger, but I have no idea about DB2 trigger. Maybe, I can create a real-time monitoring EC process to address it. what's your opinion?
B: I should maintain all transaction metadata by myself. e.g. INSERT, UPDATE old/new data, DELETE info. It is originally covered by the database, and it isn't easy to handle it squarely.
C: How to address some exception? like database rollback, the process recovery in case of any interruptions in the above steps.
Could you share me some idea, Thank you!
eilison
[email protected]

Scenarios for PI 7.1

Hi,
I am looking for different scenarios for PI 7.1, I am specifically looking for these scenarios.
1. iDoc to File
2. File to iDoc
3. iDoc to Webservice
4. Webservice to iDoc
5. Proxy to Webservice
6. Webservice to Proxy
Please do not send links for PI 7.0, I am specifically looking for PI 7.1
Thanks,
Nishant

Nishant,
THere is no much difference between PI 7.1 except webservices. File,IDOC,proxy will be similar.
Here by sending u new features of PI 7.1.Use ESOA for webservices scenario.
PI7.1 features refer this blog:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf
Advanncements of PI 7.1
1. Enterprise Services Repository as a central storage location for enterprise service definitions and lifecycle management data for all enterprise services (Concept of Folders,.
Using Folders in PI 7.1
Using Folders in PI 7.1
2. Universal Description, Discovery, and Integration (UDDI) 3.0u2013compliant services registry for runtime management of enterprise services.
XI : How To publish WSDL generated from XI to UDDI
XI : How To publish WSDL generated from XI to UDDI
WebAS : A step by step guide for Configuring UDDI registry on Local Server
WebAS : A step by step guide for Configuring UDDI registry on Local Server
3. Enterprise Service Oriented Architecture (ESOA), Global Data Types, Modeling Tool Concept.
ESOA BASICS
SAP Architecture u2013Enterprise SOA Basics
SAP Architecture Enterprise SOA Basics
Quick Guides for setting up an eSOA prototyping environment with CE, ESR, and NWDS
Quick Guides for setting up an eSOA prototyping environment with CE, ESR, and NWDS
ESA = SOA + ES ?
ESA = SOA + ES ?
PRINCIPAL PROPAGATION
Principal Propagation with SAP NetWeaver Process Integration 7.1
Principal Propagation with SAP NetWeaver Process Integration 7.1
Principal Propagation in SAP XI
Principal Propagation in SAP XI
Modeling tools in PI 7.1
Modeling tools in PI 7.1
Publish services from PI 7.1 to the Service Registry
Publish services from PI 7.1 to the Service Registry
Using CCTS in PI 7.1
Using CCTS in PI 7.1
4. Improved support for standards such as Web Service Reliable Messaging (WS-RM), WS Policy, Security Assertion Markup Language (SAML).
5. Support Business Activity Monitoring (BAM).
XI: BAM - Episode III - new super trace
The specified item was not found.
XI: BAM - Episode II - Simple Proactive monitor
The specified item was not found.
XI: BAM - Episode I - Introduction s
The specified item was not found.
6. Advanced Adapter Engine Features (Eg. Bypass Integration Engine Process)
7. Enhancement for Mapping (Eg. Re-usable User Defined Functions, Look-up function reads multiple fields, Specify mapping parameters at configuration time, Synchronous DB RFC lookups, Message Packing etc.)
SAP PI 7.1 Mapping Enhancements Series: Correct Structural Inconsistencies
SAP PI 7.1 Mapping Enhancements Series: Correct Structural Inconsistencies
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
SAP NetWeaver Process Integration 7.1: Mapping Enhancements Blog Series
SAP NetWeaver Process Integration 7.1: Mapping Enhancements Blog Series
SAP PI 7.1 Mapping Enhancements Series: Mapping Enhancements Demo
SAP PI 7.1 Mapping Enhancements Series: Mapping Enhancements Demo
SAP PI 7.1 Mapping Enhancements Series: Copy XML Subtree
SAP PI 7.1 Mapping Enhancements Series: Copy XML Subtree
SAP PI 7.1 Mapping Enhancements Series: Using Graphical Variable
SAP PI 7.1 Mapping Enhancements Series: Using Graphical Variable
SAP PI 7.1 Mapping Enhancements Series: Share User-Defined Functions
SAP PI 7.1 Mapping Enhancements Series: Share User-Defined Functions
SAP PI 7.1 Mapping Enhancements Series: Import SQL Table's Metadata
SAP PI 7.1 Mapping Enhancements Series: Import SQL Table's Metadata
MAPPING LOOK UPS
Lookupu2019s in XI made simpler
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
XI: RFC Mapping lookups (from BC to XI?)
The specified item was not found.
Use this crazy piece for any RFC Mapping Lookups!
Use this crazy piece for any RFC Mapping Lookups!
SAP XI Lookup API: the Killer
The specified item was not found.
mapping look ups RFC api
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
RFC Look up from XSLT mapping
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
Data Lookup Optimized
Data Lookup Optimized
8. Extended support for high volume scenarios
huge processing of files
Night Mare-Processing huge files in SAP XI
Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging
Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging
SAP XI acting as a (huge) file mover
The specified item was not found.
Managing bulky flat messages with SAP XI (tunneling once again) - UPDATED
The specified item was not found.
New NetWeaver Process Integration how-to guide for typical high volumen replication scenarios.
New NetWeaver Process Integration how-to guide for typical high volumen replication scenarios.
9. Business Activity Monitoring for process definition of milestone monitoring (event correlation).
10. Improved SAP NetWeaver Administrator support for central configuration and administration of both mediated and point-to-point scenarios.
11. XML payload validation and validations using JAVA.
VALIDATING MESSAGES
Validation of Messages in SAP NetWeaver Exchange Infrastructure - SDN Member Session EPI213 at SAP TechEd '06 Amsterdam
Validation of Messages in SAP NetWeaver Exchange Infrastructure - SDN Member Session EPI213 at SAP TechEd '06 Amsterdam
SOA Middleware: XML validation error handling
SOA Middleware: XML validation error handling
The Hitchhiker's Guide to Validation
The Hitchhiker's Guide to Validation
Validations using Java for those not having PI7.1
Validations using Java for those not having PI7.1
Xml validation
XML Validation BPM:
VALIDATING INCOMING FLAT FILE
Generic Approach for Validating Incoming Flat File in SAP XI - Part 1
Generic Approach for Validating Incoming Flat File in SAP XI - Part 1
Generic Approach for Validating Incoming Flat File in SAP XI - Part II
Generic Approach for Validating Incoming Flat File in SAP XI - Part II
Validating messages in XI using XML Schema
Validating messages in XI using XML Schema
BPM:
Enhancements in ccBPM within SAP NetWeaver Process Integration 7.1
Enhancements in ccBPM within SAP NetWeaver Process Integration 7.1
12. Process editor modeling enhancements: step groups, integrated alert management and configurable parameters.
13. Integration of human interaction (generic user decision).
14. Language dependent texts for end-user display.
15. WS-BPEL 2.0 adoption (Preview and implementation BPEL4People, BPLE-SPE Simple User Defined Functions can be configured directly in the process.)
Also refer this links for more clarifications:
http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/369142f195675ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/fb4cd3207c7063e10000000a1553f6/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f36ce30f-0e01-0010-a89b-c158d07c44ff
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ec19c05d-0501-0010-09a2-b6db51b5318d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5441afe5-0601-0010-dba5-dc5f9d5caa9d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c50cddbb-0601-0010-92a7-f2a40ca68e6d
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f027dde5-e16e-2910-97a4-f231046429f2
Refer these threads as well:
Advantages of using PI 7.1 over PI 7.0
PI 7.0 and XI 3.0
http adaptor on which factors we will use
Diff between XI and PI
differences between xi 3.0 and pi 7.0
Difference/ changes from XI 3.0 to PI 7.0
give me main advantages of XI-7.0 TO XI-3.0
XI 7.0 vs Xi 3.0
XI/PI
XI vs. PI
XI 3.0 vs. PI (XI 7.0)
Difference/ changes from XI 3.0 to PI 7.0
moving from XI 3.0 to PI 7
Edited by: VenkataPrabhakar Teegavarapu on Dec 2, 2008 1:48 PM

Value Mapping replication issue

Hi PI Experts,
I am working on the Value mapping replication scenario using Z-table created in R/3 system.
I have configured the value mapping Replication Out Abap proxy.
I am getting the following error :
Audit Log for Message: 4d404b41-39e4-0083-e100-80008b3557e6
Time Stamp Type Description
2011-01-27 07:56:19 Information The message was successfully received by the messaging system. Protocol: XI URL: http://gendevhrcx51.unix.appliarmony.net:54000/MessagingSystem/receive/JPR/XI Credential (User): PIAPPLUSER
2011-01-27 07:56:19 Information Using connection JPR. Trying to put the message into the receive queue.
2011-01-27 07:56:19 Information Message successfully put into the queue.
2011-01-27 07:56:19 Information The message was successfully retrieved from the receive queue.
2011-01-27 07:56:19 Information The message status was set to DLNG.
2011-01-27 07:56:19 Information Java Proxy Runtime (JPR) accepted the message.
2011-01-27 07:56:19 Error JPR could not process the message. Reason: Cannot locate proxy bean ValueMappingApplication.
2011-01-27 07:56:19 Error Delivering the message to the application using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: Cannot locate proxy bean ValueMappingApplication.
2011-01-27 07:56:19 Information The message status was set to WAIT.
2011-01-27 07:56:19 Information The asynchronous message was successfully scheduled to be delivered at Thu Jan 27 08:01:19 CET 2011.
I have followed the threads :
1) /people/udo.martens/blog/2009/04/03/value-mapping-replication-scenario
2) ValueMappingReplication in PI 7.1
3) How to Perform Value Mapping u2013 A Walkthrough -> Sarath Chandra Kandadai
which had similar issue but could not make any headway.
Questions :
1) Are there any specific PIAPPLUSER authorizations required ,I have configured the CC as per the 3rd thread.
2) There is an issue with SLD access when I look at the JPR monitoring,could be the possible reason.
SLD access SLD host:port = gendevhrcx51:54000
Error getting JPR configuration from SLD. Exception: No entity of class SAP_BusinessSystem for DHX.SystemHome.gendevhrcx51 found
No access to get JPR configuration
I have refered to the Note : 809420 and asked the basis team to look into this.
I am running out of ideas ,request you guys to help on this issue.
Thanks
-Alok

Hi Alok,
i have similar error. Here the error:
30.12.2013 20:40:17.789
Information
Java Proxy Runtime (JPR) accepted the message.
30.12.2013 20:40:17.871
Error
JPR could not process the message. Reason: No remote bean found for reference of class com.sun.proxy.$Proxy352.
30.12.2013 20:40:17.876
Error
Delivering the message to the application using connection JPR failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class com.sun.proxy.$Proxy352.
30.12.2013 20:40:17.911
Information
The asynchronous message was successfully scheduled to be delivered at Mon Dec 30 20:45:17 CET 2013.
I have registered the inbound interfaces:
http://sap.com/xi/XI/System#ValueMappingReplication = localejbs/sap.com/com.sap.xi.services/ValueMappingApplication:valueMappingReplication
http://sap.com/xi/XI/System#ValueMappingReplicationSynchronous = localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous:valueMappingReplicationSynchronous
2 interfaces found
But somehow the bean is not found and gave me the error :
JPR could not process the message. Reason: No remote bean found for reference of class com.sun.proxy.$Proxy352.
Can you tell me in detail what you have done to resolve the problem? I send the test data from soapui using the outbound interface ValueMappingReplicationOut provided by the content in SAP BASIS 7.11.
Thanks,
Ly-Na

Error while calling the java proxy with the ValueMapping repl scenario

Hi All
I am trying to upload values in the RWB for vaue mapping using the standard ValueMappingReplication interface . But I can see the following message in the Message Display Tool of the RWB .This scenario was working fine sometime back suddenly after some days we started to see this exception .
JPR could not process the message. Reason: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication
Delivery of the message to the application using connection JPR failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication: com.sap.aii.proxy.xiruntime.core.XmlInboundException: No such method valueMappingReplication (for the asynchronous replication scenario) in proxy bean localejbs/sap.com/com.sap.xi.services/ValueMappingApplication.
Can anyone please guide me what could be the done to resolve this .
Thanks.

This may happen when the java proxy is not registered. Use the following URL to do so
http://<Server>:<Port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=valueMappingReplication
Regards,
Prateek

Replication scenario

Similar Messages

Maybe you are looking for