Posting a message directly to abap engine

Hi all,
I'm developing an adapter and I wish to post directly my message to an abap engine via http, not passing through the http adapter; does anyone know how to make it? Which is the receiver service's parameters? and how to communicate using the abap proxy engine(of course via java, not via XI service)
thanx
Paolo

hi,
I belive you can copy a service from SICF
and put your class in the handler list
you can try copying adapter_plain
and the default CL_HTTP_PLAIN_INBOUND
handler and replace it with your code
but I've never done it yet so I don't know
if this is a suitable way
more:
http://help.sap.com/saphelp_nw04/helpdata/en/c6/839c4eea6f374b8e230ef4b152b110/content.htm
Regards,
michal

Similar Messages

XI Adapter ? No messages in the adapter engine in RWB

Hi Guys,
I have the scenario SOAP-PROXY. I have configured XI Adapter on the receiver side. I have used xml spy to post the messages directly to the IS. I could not see any messages in the adapter engine in RWB.
I have seen the messages processed successfully in the integration engine under RWB.
can anybody explain why i could not see any messages in the adapter engine ? Is It normal with the xi adapter on the receiver side ?
Thanks,
Raj
Message was edited by:
raj reddy

Raghu.
I've done the following:
1. I've executed SE38 tx code.
2. I've entered the "RSXMB_DELETE_MESSAGES" report as "Program"
3. As the "RSXMB_DELETE_MESSAGES" report does not have a selection screen, it must be executed with default parameters. So, I selected "Program -> Execute -> Background".
4. There are no available variants, so I clicked on the "Execute immed." button.
5. The job starts. I can monitor it on the SM37 tx code.
6. It only deleted 20 messages.
What I get from this, is that the "RSXMB_DELETE_MESSAGES" report cannot delete the big part of the messages since them are marked as "Archivable" and not as "Archived".
what do you think of it??
regards
Carlos.

Auto restart of messages failed in Adapter Engine PI 7.0 and 7.1

Hi,
I am trying to figure out a way to automatically restart the messages failed with in the adapter engine (because of the target system not available etc.). These messages are in System Error status and I can restart them from RWB. But I am looking for any report or something available either on Java or ABAP engines so that I can automate the process.
Thanks for the help.
VJ

I have come across the web service AdapterMessageMonitoring in PI 7.0 (Found it in Web service navigator) with possibly useful methods. But I could not find the same service on PI 7.1. Any clue on this?
Also, the getMessageList methods works perfectly as expected but the resendMessages mehtod fails with the exception -
com.sap.engine.services.ejb.exceptions.BaseEJBException xmlns:ns1="http://sap-j2ee-engine/client-runtime-error">Exception in method resendMessages.</ns1:com.sap.engine.services.ejb.exceptions.BaseEJBException>
Will post more if move forward.
VJ

Message Flow in Integration Engine

Dear Friends,
Kindly can someody share how the message is flowing in Intergration engine after the message taken from Adapter engine.
If you have any block diagram it will be helpful for me

Hi Karthik,
There are 6 stpes for the message processing thats only called
PIPELINE Steps.
what are all the steps involved in the Pipeline processing.
Sender Adapter picks up the file from the file system, converts it to XML and places it in the payload of an XI-SOAP message. Then it posts this message to the Integration Server pipeline via http(s).
XI pipeline steps are:-
->Sender Agreement
->Receiver Determination
->Interface Determination
->Interface Mapping
->Receiver Agreement.
When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:
1) Receiver Determination: This steps determines the system that participates in the exchange of the message.
2) Interface Determination: For each receiver determine which interface will should receiver the message.
3) Message Split: If more than one receivers are found, Xi will instantiate new message for each receiver.
4) Message Mapping: Mapping to transform the source message to destination message format.
5) Technical Routing: Bind a specific destination and protocol to the message.
6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.
One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.
message flow in XI
The life cycle of the message is explained in detail by taking an example scenario. The file is picked up by the Sender File adapter and the data is inserted into DB table by Receiver DB Adapter.
       The adapter engine uses the messaging system to log the messages at every stage. This log is called the Audit Log. The audit log can be viewed from the runtime work bench (RWB) to look into the details of the lifecycle of the message. During our journey we will also have a look at the messages that are logged at different stages.
Note: This article is targeted for the newbieu2019s who want to understand the message flow in Adapter Engine. So the insight into the message lifecycle is provided here by taking only the Technical adapters (File/ JDBC/ JMS/ Mail) into consideration. It doesnu2019t delve into the lifecycle of the messages that have reached XI Adapter Engine using RNIF/ BC/ CIDX adapters.
ONWARD JOURNEY:
Fig1. Message flow from Adapter Engine to Integration Server
1.     For the message to be picked up by the communication channel, the channel should be associated with a sender agreement. Here creation of a communication channel doesnu2019t ensure the message to be polled and picked up by the adapter. The message reaches the adapter in its native message format. As the communication in SAP XI happens in XI message format, a module inside the adapter converts the message in native format into XI message format.
2.     During this process, a message ID is generated for the message. To build the XI header (sender agreement details like the sender system, sender message interface and the interface namespace) the details are fetched by performing a CPA lookup(collaboration-partner-agreement are the configuration object details that have been created using the configuration time. The details are updated into the runtime cache when you activate the Configuration objects in Integration builder u2013Configuration time. This cache is referred to as CPA cache).
3.     This message is then sent to module processor for further processing. During the process of sending the message to module processor, the message u201CApplication attempting to send an XI message asynchronously using connection AFWu201D is logged.
4.     The module processor performs steps like structure conversion, communication channel specific conversions (that have been specified in the u201Cmodule tabu201D of the adapter channel). These conversion modules are executed in the same sequence as mention in the communication channel.
5.     After the successful execution of the conversion modules, the appropriate module (call SAP adapter module) of the module processor is called which will send this message for persistent storage. This message is put into the Send Queue of the messaging system for further processing. Messages like u201CMessage trying to put into the send Queueu201D and u201CMessage successfully put into the queueu201D are logged during this process. A confirmation message (success/ failure) is sent back to the sender application at this stage. This confirmation message is used by the channel to perform various steps like deleting the file that has a processing mode as delete.
6.     The message that has been put in the Send Queue has to be picked up and sent to the Integration Engine. The Adapter Engine and XI Integration server use XI Adapter for internal communication purposes. So the XI Adapter picks up message from the send queue and parses the XI message. In this process, the status of the message is set to DLNG and. Messages like u201CThe message was successfully retrieved from the send queue and message status set to DLNGu201Dare logged.
7.     The XI adapter performs a SLD look up (System landscape Directory) to find the Integration server with which the Adapter framework has register itself.
8.     On successful SLD look up, the message is sent via HTTP to the XI IS pipeline, using the pipeline URL (http://hostname:abap-httpport/sap/xi/engine?type=entry). . If this is successful, a message u201CThe message was successfully transmitted to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFWu201D is logged and the message statues is set to DLVD means message has been successfully delivered to the endpoint( XI IS in this case)
Fig2. Audit Log of message during onward journey
RETURN JOURNEY:
The return journey commences when the IS has successfully processed the message and delivers it to the Messaging system using the URL u201Chttp://hostname:50000/MessagingSystem/receive/AFW/XIu201D
br>
Fig3. Message flow from Integration Server to Adapter Engine
1.     When the Integration Server (XI IS) finishes processing of the pipeline steps (like receiver determination, interface determination and interface mapping), the message has to be delivered to the required Receiving system. So the XI Integration server will send the message to the messaging system of the Adapter Engine (AE) using the mentioned above. Once the message is successfully received by messaging system, the message u201CThe message was successfully received by the messaging system. Profile: XI URL: http://hostname:50000/MessagingSystem/receive/AFW/XIu201D is logged.
2.     As discussed Integration server and Adapter Engine use XI adapter for internal communication purposes. So the XI message that has been received by the messaging system URL is parsed by the XI Adapteru2019s protocol handler.
3.     The XI message is put into the receive queue and persisted. During this stage messages like u201CUsing connection AFW. Trying to put the message into the request queue; Message successfully put into the queue.u201D are logged.
4.     The XI messages that are put in the receive queue are retrieved by an application (Worker thread) and are sent to AFWListenerBean. AFWListenerBean is a module (an EJB) in Adapter Engine that is capable of parsing the XI message. On successful receive of the XI message by the AFWListenerBean, messages like u201CThe message was successfully retrieved from the request queue.u201D are logged and the status of the XI message is set to DLNG.
5.     The AFWListenerBean reads the receiver agreement and the corresponding channel from the XI header to determine the appropriate adapter. In this stage the adapter channel is logged in the audit log. u201CDelivering to channel: XYZ_Channelu201D
6.     The message is forwarded to the module processor where additional steps like structure conversions and extra modules specified in the adapter are performed.
7.     The exit module is called and the message is sent to the appropriate adapter (DB Adapter in this case). The format conversion will be executed within the specific adapter and sent to the Receiving system (DB in this case) using the channel that has been determined by the AFWListenerBean and the required action is reformed (select statement is performed in this case). On successful processing of the message the status is set to DLVD.

Auto Cancellation of Messages in the Integration Engine.

Dear all,
Issue: Auto Cancellation of Messages in the Integration Engine.
Description: Actually Today, I'm facing Problem in message mapping and its showing error "JCO_SYSTEM_FAILURE". Finally the message is Auto Canceled and showing the status in the Message Monitoring as Canceled with Errors.
I have doubt here how the messages are Auto Canceled with Error? Is there any system or ABAP program which cancelling these messages?
Waiting for yours valuable reply on the above issueu2026
Edited by: BhavinPatel on Oct 7, 2010 8:15 AM

Hi Bhavin,
Two report program are there to cancel error msgs automatically..
1) RSQIWKEX
2) RSXMB_CANCEL_MESSAGES
Regds,
Pinangshuk.

XI message status at Adapter engine level using a table (SAP table)

Hello Experts,
XI message status at Adapter engine level using a table (SAP table).
We want to write a custom report using ABAP so Pls tell why the status u2018Holdingu2019 and u2018To be deliveredu2019 are present in message monitoring of RWB but not in the status (MSGSTATE) field of SXMSPMAST table.
My need is to write a report to get the messages based on the these status from table level.
Please let me know the table name and field name for this and the table name for the desciption of the status of XI messages at Adapter level.
Thanks
Gopesh

Hi Gopesh,
the Adapter Engine Messaging System messages are on the Java schema,
i.e., see the following -
[XI/PI tables|https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/xi+tables]
Regards
Kenny

How to get Payload of SOAP Message in Advance Adapter Engine

HI All,
I am wondering if anybody can tell me how to view the Payload of SOAP Sender and Receiver Message in Advance Adapter Engine?
Does Anybody know how to check mapping payload in Advance Adapter Engine because in ABAP you can see the mapping payload under Request Message Mapping but when you use AAE you can't see the Request Message Mapping Payload.
I have a SOAP to RFC Scenario in which I can't see the SOAP Sender and RFC Receiver Mapping Payload.
When I am sending incorrect data to an RFC I am getting this error which is very strange and new to me.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to split a synchronous message
Any comments would be much appreciated.
Thanks,
Iqbal

HI All,
I have managed to find Michal's Blog which is talking about getting the mapping payload but unfortunately I don't know how to create Adapter Module so I am wondering if somebody can please provide me EAR file so that I will request the Basis guys to deploy the code and hopefully this will solve my query.
Michal's Blog
As you all probably know while using local Advanced Adapter Engine (AAE) processing in SAP PI 7.1 the message is logged only once (during processing by sender adapter). This is great in terms of performance but what if we need to check the mapping output? Is there a way do do it somehow? It turns out that we don't have such an option in standard yet. Is there any alternative then?
It turns out there is - a simplest adapter module there is...
Local AAE works in such a way that from the sender adapter it executes the receiver adapter so in the outbound message to PI processing you can see the adapter info logs of the receiver adapter and this is what we can use. The idea is to add an adapter module to the receiver adapter which will put the content of the message into the audit log of PI message processing. We can do it by writing a few lines of code:
PI/XI: target message logging with local AAE not possible ? not anymore...
*Please upload the file in any free site or <REMOVED BY MODERATOR>
<READ RULES OF ENGAGEMENT>
Thanks,
Edited by: Prateek Raj Srivastava on Jan 6, 2012 9:10 PM

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

No message reach into Integration Engine ...

Hello,
I have following problem. I send message to XI through SOAP adapter. But the message doesn't reach of Integration Engine. It is delivered into Adapter Engine and then it stays in status "Waiting". When open message detail in RWB I get these information:
Message Data
Attribute     Value
Engine     Adapter Engine
Status     Waiting
Repeatable     Yes
Cancelable     Yes
Start     29.08.2008 12:14:59
End     29.08.2008 12:14:59
+Sender Party     +
Sender Service     BS_GetSupperior
Sender Interface     http://sntcz.cz/xmlns/holidays
MI_Holiday
+Receiver Party     +
+Receiver Service     +
+Receiver Interface     +
Quality of Service     Exactly Once
Error Category     XI_J2EE_ADAPTER_XI_HANDLER
Error Code     GENERAL_ERROR
Message     55C9628075B311DDABE200301875333B
+Reference     +
... and in defaultTrace file occures this message:
#1.5#00301875333B0057000000DE0000109C00045596D2CD72D8#1220006176812#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XISUPER#18255d00759d11ddc1a500301875333b#SAPEngine_Application_Thread[impl:3]_31##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#
#1.5#00301875333B004B0000009D0000109C00045596D2CE9B64#1220006176890#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#XISUPER#2919##srvbr05_NW4_2798750#XISUPER#ecff64f075af11dda90200301875333b#XI SOAP[BS_GetSupperior_SOAP/BS_GetSupperior/]_2449##0#0#Error##Plain###no message ID available#
#1.5#00301875333B0049000001270000109C00045596D3111C00#1220006181250#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#sap.com/com.sap.xi.mdt#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#XISUPER#2920##srvbr05_NW4_2798750##f03f74c075af11ddb4ce00301875333b#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###enrichMessageData(): Error during retrieving the end-to-end-monitoring information
Thrown:
com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception:
     at sun.reflect.GeneratedConstructorAccessor358.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
     at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:82)
     at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
     at com.sap.aii.rwb.endtoendmonitoring.util.PMI_PortType.sxmb_Get_Pmi_Info(PMI_PortType.java:28)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:965)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:762)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:568)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl0.getPureMessageList(MessageMonitoringObjectImpl0.java:1016)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1772)
     at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:354)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:744)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:552)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:657)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:810)
     at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1254)
     at jsp_monitor_new1219936385390._jspService(jsp_monitor_new1219936385390.java:9)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     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)
If I try to send message to XI directly through HTTP adapter the message is not delivered into Integration Engine.
Do you have any idea what to check or where could be problem?
Thank you in advance for every advice!
Best regards,
Zbynek

Hi Zbynek,
I think the problem is in the structure of the xml you want to send. I mean, that the structure of the message you are sending by means of SOAP adapter is not the same that the structure in the Inegration Repository.
When you test your message with a wrong BS it is sent to the IE and you can see this message in sxmb_moni with error status. It`s obvius, there is no configuration for this scenario. However if you test your scenario with right parametes but the content (xml structure) is wrong, the step when the content of the call is converted to the structure of the IR will fail. And the message doesn`t get the IE.
So check the content of your call.
I hope it is useful for you.
Regards,
Carlos

Message struck in adapter engine with status Hold

Hi,
In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
Regards,
Krishna

Hello,
Below is some information on how to resolve this type of issue:
1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
4 - Sort the messages in ascending order based on the Sequence no.
5 - Check the predecessor message of the first message in status "HOLD"
Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
a - Predecessor is in Failed State/System Error : Cancel/Resend the
first message in status HOLD after this. Then the remaining messages
can be cancelled/resent.
b - Predecessor is in DLVD state(delivered state) : First Holding
message can be resent/cancelled followed by the others.
c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
predecessor message failed and correct the reason for the failure.
Then resend the predecessor message and then cancel/resend the
remaining HOLD messages. Alternatively, you can directly try
resending this NDLV predecessor message and see if it goes. If it
goes, then the remaining HOLD messages can be resent/cancelled.
Another option could be to cancel this NDLV predecessor message so
that it goes to FAILED state and then cancel/resend remaining HOLD
messages.
Regards,
Sarah

Hi, I don't really know wether I should post this message in the iPad sect

Hi,
I don't really know wether I should post this message in the iPad section or in this section... Anyway.
Here is my problem :
I would like to stream music from my iPad to my living room soundsystem, so I bought an Airport Express. BUT my router is upstairs, and I can't set up a permanent Ethernet connection between my router & Airport Express.
So my question is : Is it possible to set up the Airport Express as a "distinct network" (not connected to the internet) and Have the iPad connect on Both networks ?
* my usual LAN to surf the net & everything else
* The airport Network to stream music to the soundsystem
If my setup is wrong, i'm obviously open to any advice... Just keep in mind that I can't have a wired connection between the Airport Express & the Router...
Many thanks in advance for your answers.

Before to close this topic and mark it as solved, I will explain the whole process, so if you find this, you can try it directly... French version hereunder.
Hardware setup :
- Bbox2 Modem router provided by my ISP
- PC with latest version of Airport Utility
- Airport Express connected to amplifier (Jack - Double RCA) and to the router through Ethernet (the whole purpose of this is to remove this Ethernet cable).
Before you begin :
Open your router configuration utility (typically 192.168.1.1 or 192.168.0.1 in your browser). Change your network password (by default, mine was the 26 characters WEP key - 13 letters and 13 numbers). Choose a 13 characters password. I chose one with 7 letters followed by 6 numbers. Waring : This operation might (should ?) crash your current internet connexion and you may experience problems reconnectiong. Under Win 7, Go to the properties --> security of your network to type your new password & connect again.
Once this is done :
1. Open the Airport Utility on your computer
2. Do a "hard reset" of the Airport Express" (AE) using a pen or a paperclip --> the AE disappears from the Airport utility, then shows up again.
3. Select "replace the settings with default settings" to clean up the mess your previous attempts might have caused
4. You're back to the default configuration
5. On the Airport utility window you see now, invent a new password for the AE & clic continue
6. Select "I want AE to join my current network" (3rd option), clic on "Continue".
7. Select "I want AE to wirelessly join my current network" (1st Option), clic on continue
8. Select your network in the drop down menu and select "WEP 128 bits" as encryption mode (Your network obviously has to use WEP encryption. If it's not the case, go back to your router management utility and set the security to WEP or write another tutorial
9. Clic on "Update"
10. Watch your LAN crash
11. Say "What the F**" and unplug the Ethernet cable from the AE. Your LAN should get better very quickly.
12. Accidentally unplug the AE from the wall. Plug it again quickly with 2 or 3 "Sh** !"
You're done !
French version :
Préalable :
Configuration hardware :
- Modem router Bbox2 fourni par mon FAI (Belgacom)
- PC avec la dernière version de Airport Utility
- Airport Express connecté à un ampli (Jack - Double cinch) et au routeur via un câble Ethernet (le but de la manoeuvre est de virer ledit câble Ethernet)
Ouvrir l'utilitaire de configuration de votre routeur (192.198.1.1 dans le navigateur par exemple) et changer là le mot de passe du réseau (anciennement chez moi : la clé WEP de 26 caractères) en choisissant un mot de passe d'exactement 13 caractères (chiffres et lettres mêlées ont fonctionné pour moi). Attention, cette opération peut avoir des retombées un peu bizarres sur votre connexion... Deux redémarrages de Bbox et pas mal d'essais de reconnexion m'ont été nécessaires.
Une fois cela fait :
1. Ouvrez l'Airport utility
2. Opérez un Hard reset de l'airport avec un trombone --> l'AE disparait de l'utility, puis réapparaît
3. Sélectionner "Replace the settings with default settings" histoire de virer tout merdier d'essais précédents.
4. Vous êtes de retour à la configuration "de base"
5. Sur l'écran qui s'affiche alors, inventez un nouveau mot de passe pour l'AE puis Cliquez sur "continuer"
6. Sélectionnez "I want Export Express to Join my current network (3ième option)" puis cliquez sur "continuer"
7. Choisissez "I want AE to wirelessly Join my current network (1ière option)" puis cliquez sur "continuer"
8. Sélectionnez votre réseau dans la liste déroulante et sélectionnez "WEP" comme mode de cryptage (il faut évidemment que votre réseau soit crypté en WEP. Si ce n'est pas le cas, passez en WEP ou faites un nouveau tuto...
9. Cliquez sur "Update"
10. Regardez votre réseau local se planter en beauté...
11. Débranchez le câble de l'AE. Le réseau local devrait se sentir beaucoup mieux
12. Retirez accidentellement l'AE de la prise. Rebranchez-le vite fait avec 2-3 "Mert".
You're done !

XSLT Mapping on ABAP Engine

Hi All,
I am trying to implement an XSLT mapping on the ABAP Engine. I went to the Transformation Workbench(SE80).I have created 4 levels of packages (Structure->Main->then 2 more levels) and included Package Interface SAI_TOOLS in 'Use Accesses' tab.
I have also set com.sap.aii.repository.mapping.additionaltypes=R3_ABAP|Abap-class;R3_XSLT|XSL (ABAP Engine)
in the Exchange Profile.
Now I want to create the tranformation (ST or XSLT) so that I can see it in the Repository.
At which package level(1st to 4th), should I right-click and go to 'Create->More->Transformations' so that I can see this XSLT Mapping program in the repository?
I have followed all the links from help.sap.com but I am unable to get the desired result, i.e. see my Mapping in the Repository when I choose Mapping Program of type 'XSL->ABAP Engine', from the drop-down box in Interface Mapping.
Kindly help.
Regards,
Puloma.

Hi Naveen,
I did as you told, i.e. keyed in the name of the ABAP Transformation program (mapping) name.I have not written any namespace for the Mapping program in the Interface Mapping Design, just the Program name.
When I execute my mapping from se80, it works perfectly.
I created this Transformation program at the topmost level (i.e. Structure package level).
But when I execute my scenario, I get the following runtime error in sxmb_moni:
Error in mapping program zpc_transfom2 (type R3_XSLT, kernel error ID UNCAUGHT_EXCEPTION).
What is wrong? Did I create the transformation program at the wrong level?
Regards,
Puloma.

How can I dial a phone number from an email message directly

How can I dial a phone number from an email message directly,
But even before the selection i will change or correct the number?
If I copy the number in the notebook, all spaces are filled with % signs.
When I dictate SIRI the number I get the answer: I do not know the number
If I copy the number in the phone selection (above) the number can not be edited afterwards.

You can dial a number appearing in an email by tapping on it.
But if you need to correct the number first you cannot edit a received email.
To edit the number tap on the forward symbol and when the draft comes up you should be able to correct the phone number, copy it and paste into your Phone App. Then delete the forward email without sending it.

Am trying to upgrade iphoto and other applications , but app store is posting a message "To update this application, sign in to the account you used to purchase it." KNOWING THAT I ONLY HAVE ONE APPLE ACCOUNT AND 2 MACS

Am not sure how to solve this issue ,, but i had an old MAcBook Pro that i was using with for somt time and i got a notre MACBook pro and on both of them am using the same apple accouny to purchase or download application . . now APP store is not allowing to upgrade or purchase any applications on my newest MAC posting this message " To Update this application , sign in to the account you used to purchase it" .. and could not find a solution to this by signing out and in didnt work ,, any clues is much appreciated..
Cheers
Hesham

Thanks for you reply. I'm 99% positive that I'm using the user id and password that I used to set up my computer. That's why I'm stumped. I read the solution someone else suggested (type your user name without @gmail and create a new password. When I tried it, I was asked for my birthday. It didn't recognize it. I know I got my birthday correct. Oh well...
Karen

RFC destination from XI ABAP engine to 4.5 B system

I tried to create an RFC destination from XI ABAP engine to 4.5 B system.
It does not work and gives an error.
<b>Error Details DETAIL: NiIGetSockName</b>
-Naveen.

Hi Naveen,
First of all try to ping 4.5B system from XI system (Through TELNET)... This is to ensure the connectivity and the access. The error is not a common error, i suppose, So better first we check the phisical connectivity...
Plz. confirm...
Regards,
Audy

Posting a message directly to abap engine

Similar Messages

Maybe you are looking for