puri visit

-

 

https://www.google.com/maps?q=19.81221,85.8252783&z=17&hl=en


room booking 1day 1500, 10members( near temple)




19°48'42.0"N 85°49'38.8"E - Google Maps


19°49'00.0"N 85°50'18.4"E - Google Maps


19°48'23.9"N 85°50'12.6"E - Google Maps


19°48'19.6"N 85°50'09.3"E - Google Maps





Popular posts from this blog

SAP CPI : camle expression in sap cpi , cm, router, filter and groovy script. format

-
Image
  --------------------- Using Camel Simple Expression Language Cloud Integration  supports a subset of the expressions defined in Camel Simple Expression Language (see  https://camel.apache.org/components/next/languages/simple-language.html  ). You can use Camel Simple Expression Language when configuring the following components: Components that Support Camel Simple Expression Language Component Use Camel Simple Expression to ... More Information Content modifier Define: Message body Message header Exchange property ( Type  parameter set to  Expression ) Define Content Modifier Write variables Define a variable. ( Type  parameter set to  Expression ) Define Write Variables Router Define a routing condition. ( Expression Type  parameter set to  Non-XML ) Define Router Content filter Define conditions for XPath elements. To review some examples, see  Examples . Define Filter Expressions Supported by Content Modifier and Write Variabl...
Read more

SAP CPI camel conditions and xpath conditions

-
  ------------------------------------ Context You perform this task when you have to specify conditions based on which the messages are routed to a receiver or an interface during runtime. If the message contains XML payload, you form expressions using the XPath-supported operators. If the message contains non-XML payload, you form expressions using the operators shown in the table below: Usage of Operators in Non-XML Conditions Operator Example = ${header.SenderId} = '1' != ${header.SenderId} != '1' > ${header.SenderId} > '1' >= ${header.SenderId} >= '1' < ${header.SenderId} < '1' <= ${header.SenderId} <= '1' and ${header.SenderId}= '1' and ${header.ReceiverId} = '2' or ${header.SenderId}= '1' or ${header.ReceiverId}= '2' contains ${header.SenderId} contains '1' not contains ${header.SenderId} not contains '1' in ${header.SenderId} in '1,...
Read more

chatgpt explanation: all retry messages in sap cpi, with example using jms sender.

-
  https://help.sap.com/docs/cloud-integration/sap-cloud-integration/configure-jms-sender-adapter https://api.sap.com/integrationflow/Replicate_Vehicles_from_SAP_S4HANA https://api.sap.com/integrationflow/Replicate_Vehicles_to_SAP_Digital_Vehicle_Hub You're working with two SAP CPI iFlows involving a JMS-based retry mechanism. Let's break this down and explain how retry logic works , based on your configuration and screenshots. 🔁 High-Level Scenario iFlow 1 : Sender : HTTP or any other adapter. Receiver : JMS queue (e.g., VMS_DVH ) . Goal : Buffer/queue the request into JMS for reliable retry handling. Important Params (JMS Receiver): Maximum Retry Interval (in min) Retry Interval (in min) (These define how CPI will re-enqueue a message for retry.) iFlow 2 : Sender : JMS Sender (e.g., from VMS_DVH ) Receiver : Final endpoint (e.g., S/4HANA, DVH, etc.) Contains Retry Logic based on ${header.SAPJMSRetries} Branching logic is something li...
Read more