Messaging Server 4.15 Plug-in API

I need to convert a messaging server 3.6 plug-in into a messaging server 4.15 plug-in.
I got the messaging server 4.15 plug-in API guide. I wrote a plug-in. Building the SMTP plug-in is OK. I installed this plug-in by configuring the SMTP plug-in configuration file /iplanet4/msg-citi38seu02/smtp-bin/plugins/plugins.conf :
PostSMTPAccept /iplanet4/msg-citi38seu02/smtp-bin/plugins/AGORAplugin.so funcs=PluginReadMessage init=PluginInit
When the configuration was OK, I restarted the smtpd process.
The plugin had no effects on sent messages.
What could appen?
Platform : AIX 4.3.3
Messaging Server : Iplanet Messaging Server 4.15
Thanks

What is the expected result of the plug-in?
Also, if you set the smtp log level to debug do you see it initializing the plugin at startup time and also entering the plugin during the smtp-accepts?

Similar Messages

Migrating from Netscape Messaging Server 4.15 Plug-in to iPlanet Messaging Server 5.1 Channel

Hi, there.
I wrote a custom plug-in for Netscape Messaging Server 4.15. The client for
whom I did this is now upgrading to iPlanet Messaging Server 5.1 and has
requested that I update the custom plug-in accordingly. Unfortunately, as
specified in the iPlanet migration documents, you have to re-code the
plug-in as a channel to get it to work under iPlanet Messaging Server...
I've scoured the documentation about how to go about doing this, but I don't
know how to get started as I don't know anything about writing a channel.
The plug-in processes incoming messages to see if they were sent from a
specific domain. It then adds an arbitrary signature to each appropriate
MIME part in the message before letting the messaging server relay it.
1. Can anyone direct me to some explicit directions about how to write a
channel for iPlanet Messaging Server? The documentation for Netscape
Messaging Server was extremely helpful; I haven't found anything equivalent
for iPlanet channels.
2. Channels run as daemons? Do you have to start them when the machine
boots, or are they started for you by the MTA as a result of the channel
configuration file?
3. Do channels listen with sockets on a particular port for communication?
Do I have to parse incoming data and encode outgoing data as if it was an
SMTP communication?
4. Can an SMTP channel co-exist with other SMTP channels on the same
machine? Do the channels have to listen on unique ports? (Sorry, my socket
programming is a little rusty.)
Anxiously awaiting your reply...
Sean Dockery
[email protected]

What is the expected result of the plug-in?
Also, if you set the smtp log level to debug do you see it initializing the plugin at startup time and also entering the plugin during the smtp-accepts?

Where can i find the IPlanet Messaging Server API

I am trying to log a user into the IPlanet Messaging Server when the user logs into the IPlanet Portal Server. I would like to create a SSO effect between the portal server and the messaging server.
Thanks

Check out the documentation for PMDF API and SIMS API. The MTA comes from PMDF. I just did a quick check and could not find out when documentation will be out regarding iMS-MTA API.
For what you want to accomplish I don't think the MTA-API is where you need to be looking. I know that ME and iDA SSO can be enabled, and I think it can be done with Portal as well, but I do not know how.

JCo APIs fail with Message Server

Hi Experts,
I use JCo 2.0 to interact with SAP System via Message Server.
When My application try to connect, it's generated this error:
Connect_PM MSHOST=HOST, R3NAME=XYZ, GROUP=GROUP
ERROR       service 'sapmsXYZ' unknown
TIME        Tue May 19 15:09:28 2009
RELEASE     620
COMPONENT   NI (network interface)
VERSION     36
RC          -3
MODULE      nixxi_r.c
LINE        2606
DETAIL      NiIServToAddr
COUNTER     7
.^.
What is the problem?
Thanks.
Marco Genova
Edited by: m.genova on May 19, 2009 4:23 PM

Hello,
The services mapping (name vs. TCPor UDP port number) are specified in /etc/services or the corrsponding file for your OS.
Obviously "sapmsXYZ" is missing there. sapmsXYZ should match the TCP port of the message server.
Kind regards,
Tsvetomir

SR Log Error - | Message : com.sap.esi.uddi.sr.api.exceptions.SRException

Hi,
We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
SR Log Error
| 11-Nov-11 14:10:45.568
| Method   : getClassificationSystems()
| Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
| ThreadID : 146
| Message : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name= ConfigurationFlags'
|
|       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
|       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
|       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
|       $Proxy1087.getClassificationSystems(Unknown Source)
|       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
|       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
|       SoapServlet.doPost(SoapServlet.java:51)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
|       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
|       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
|       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
|       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
|

Hi,
Refer Error:Service Registyr Configuration PI 7.11
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
Thanks,
Chandra

Error message "Unable to load plug-in type"

Hi I used plugin registration tool and updated an existing plugin by a new dll.. and then afer that I started recieveing error messages on the CRM on our Dev environment. Error message "Unable to load plug-in type" it was registered for contact entity for
post create and update but we are getting this error on any entity updates and creates..
Any help on how to resolve this issue with be deeply appreciated.
thanks in advance,
Future MVP

While this thread is 3 years old, yet I just encountered the same problem about half an hour ago, and I believe this is a bug within CRM Solution Import routine.
What I had was a plugin which was imported previously. Then, I added new plugin steps and got 'Unable to load plugin type' when registering the new plugin steps I added.
The solution I have is:
a. Import just the plugin assembly without the new plugin steps, and publish.
b. The plugin assembly is now updated with the new plugin class definition. Then add the new plugin steps and import the solution again.
c. The solution should now be imported successfully.
What I believe the bug is CRM Solution Import routine checks for the plugin class/type definition in the existing plugin assembly in the server rather than the new plugin assembly in the solution being imported.
By the way, all solutions are unmanaged. Perhaps, the same bug will not happen in Managed solution.
HTH anyone else experiencing the same issue.
Henri

Exception NoClassDefFoundError while using the plug-in API IResource

hi,
i am trying to use the plug-in API IResource .
for this i have included the necessary jar files.
when i am using the class Iresource in my application then it is throwing the following exception :
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.sap.app.FileAppView. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:487)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:524)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:371)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
 ... 31 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/core/resources/IResource
 at com.sap.app.wdp.InternalFileAppView.<init>(InternalFileAppView.java:90)
 ... 36 more
can anyone suggest hte solution to this?
Regards,
Ashish

Greg,
Have you been able to resolve this problem? I have a user complaining of the same thing and have not seen a resolution posted anywhere.
Thx, Rich

Unable to connect to SAPNet message server

Hi,
after starting the SAProuter, i have to check if i am able to connect to SAPNet message server.
Here is the message delivered after configuring technical parameters:
Unable to connect to SAPNet message server
Is the problem coming from the saprouttab file?
Here is my configuration of my saprouttab file :
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <SAProuter's Server IP Adress> <Port Number>
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 3299
P <SAProuter's Server IP Adress> 194.39.131.34 3299
D * * *
Thanks for your help.
Pascal.

Hi,
yes when i go to
start -> run -> drivers -> etc -> hosts file and i add the command that you suggested to me.
Here is the log file content :
Fri Mar 21 10:55:17 2008 INIT LOGFILE
Fri Mar 21 10:55:17 2008 READ ROUTTAB ./saprouttab o.k.
Edit :
when i run only those command from the saprouttab fil:
P * sapserv2 sapdp99
P sapserv2 <solution manager IP adress>
and after running the SAProuter, it seems to recognize sapserv2 but still have the problem with sapdp99.
Do i have to add sapdp99 with its 3299 port number in the hosts file?
trc file: "dev_rout", trc level: 1, release: "700"
Fri Mar 21 11:01:29 2008
SAP Network Interface Router, Version 38.10
command line arg 0: saprouter
command line arg 1: -r
command line arg 2: -S
command line arg 3: 3299
command line arg 4: -G
command line arg 5: saprouter.log
command line arg 6: -K
command line arg 7: p:<Distinguished Name>
SncInit(): Initializing Secure Network Communication (SNC)
 PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/32/32)
SncInit(): Trying environment variable SNC_LIB as a
 gssapi library name: "E:\usr\sap\saprouter\sapcrypto.dll".
File "E:\usr\sap\saprouter\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SECUDE 5/GSS-API v2
main: pid = 3860, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: './saprouttab'
***LOG Q0I=> NiPGetServByName: service 'sapdp99' not found: getservbyname [ninti.c 489]
ERROR => service 'sapdp99' unknown, skip line 29 [nirout.cpp 7923]
Edited by: Franu00E7ois-Xavier LEVY on Mar 21, 2008 11:02 AM

JCo destination/ SLD configuration/ message server GRANT POINTS!

Hi,
I am trying to create JCo Destination, using wizard when I get to the point 3.2 (message server) I do not have my message server listed in the drop down list, althogh it is up running on port 3601.
Here is an error message I ve got at the end.
SLD Data supplier service running and I have HTTP and RFC configuration in place
Thanks Denis
Failed to create new JCO client connection HR_Human_Resouces_Test: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_MsgServJCODestination.CreationClassName="SAP_MsgServJCODestination",Name="HR_Human_Resouces_Test",SystemCreationClassName="SAP_J2EEEngineCluster",SystemName="DE1.SystemHome.sbdevsqlsap2" at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:215) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:147) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:660) at com.sap.lcr.api.cimclient.CIMOMClient.createInstance(CIMOMClient.java:642) at com.sap.lcr.api.cimclient.CIMClient.createInstance(CIMClient.java:730) at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.createInstance(JavaCIMObjectAccessor.java:44) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:283) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Hi Denis,
The below is the Wiki which i have created, please go through the notes.
Configure SLD for JCo and Creation of JCo Destinations
To create JCo connections you need to configure SLD (System Landscape Directory) first and then create JCo destinations.
First lets see as how to configure SLD.
Start Visual Administrator.
To start it
1) Go to Server Installed path i.e. usr\sap\<systemid>\<systeminstance>\J2ee\admin
2) Choose go.bat and start it.
3) Under Global Server Configuration, choose <Serverid>.
4) Choose Services under it.
5) Find SLD Data Supplier.
6) Under System Landscape Directory select HTTP Settings.
7) Give all the required fields like Host Name, Port Number, User Name and Password.
8) Similarly choose CIM Client Generation Settings and give Host Name, Port Number, User Name and Password.
9) You can test the SLD is configured properly or not. Just click CIM Client Test.
10) Save the settings and close Visual Administrator.
Now that you have configured SLD through Visual Administrator, we can create JCo Connections. To create JCo connections
1) You will need Super Administrator permissions to create JCos.
2) Log on to the Portal.
3) Go to Content Administration  Web Dynpro
4) Since we have configured SLD, now we can see a button to Create JCo Destination. Click it
5) Now you can observe Create new JCo Destination on right side panel.
6) Give the Following Details.
a) General Data:
Name: Give the name of JCo
Client: Give the Client number to which system you want to create JCo for. Click Next.
b) J2EE Cluster: Check the Use Local J2EE engine. Click Next.
c) Connection Type: Select Dictionary Meta Data. Click Next.
d) Application Server Connection: Select the existing Message Server and Logon Group.
It might sometimes happen that Message Server and Logon Group is not configured to configure them, follow the process
For Message Server:
i. Log on to SDL through portal i.e. http://<servername>:<portnumber>/sld
ii. Choose Technical System. Click it.
iii. You will observe New Technical System button, click it.
iv. System Type: Select Web AS ABAP , if you want to connect to R/3 System and incase you are using Java application use Web AS Java
v. General: Log on to R/3 System through SAP Log on pad. Go to System  Status, check for SID, Installation Number and Database Host Name.
vi. Central Servers: Give Host Name and Port Number and Instance Number.
For Logon Group:
i. Click on Add New Logon Group, this will open a row in the table.
ii. Log on to R/3 through Logon pad and get Logon Groups ids and the transaction code is SMLG.
vii. Application Servers: Click on Add Application Server and then give Host Name and Instance Number of R/3 System.
viii. Clients: Give Client number (System id) and Logical Client Name (which we can get from SMLG code). And click finish.
7) Message Server Connection:
i. Name: Give the logon name of R/3 System
ii. Password & Confirm Password: Give appropriate password of R/3 System.
8) Click Finish.
regards
Anil

Can a customer extend Messaging Server cryptographic capabilities?

One more question was brought up internally: is it possible to integrate Messaging Server and the related components with a third-party cryptographic software in order to extend SSL and Certificate authentication?
There's certain development in JCP (Java 1.6 crypto) which has hooks for adding algorithms; perhaps it can be used to extend Access Manager and similar Java web-apps. But Messaging Server, Web/App Server, etc. engines are not quite Java... is there a way to extend them with some API, command-line calls, etc.?

shane_hjorth wrote:
JimKlimov wrote:
New cyphers, I believe, or both. Particualrly, I wondered the Russian GOST crypto stack.I've asked the developers what would be required to provide support for this encryption routine.Messaging Server uses the NSS libraries to provide the various cipher-suite:
http://www.mozilla.org/projects/security/pki/nss/
If you wanted to get the GOST cipher suite implemented the best place to start would be to ask on the mozilla newsgroup (mozilla.dev.tech.crypto) although as was pointed our by a Messaging Server developer, implementing the GOST suite is far from straight-forward which may explain why nobody has implemented it till now.
I did however find the following RFC which may help your endeavours:
http://www.faqs.org/rfcs/rfc4357.html
Regards,
Shane.

Logon balancing error:cannot connect to message server (rc=9)

Hi Gurus,
I have just installed SAP GUI 710 in my new system and copied the saplogon.ini file to the respective folder in the new system.
I am now able to see the servers in the logon pad but not able to login .
When i try clicking the logon i am getting the below error message "
"Logon balancing error:cannot connect to message server (rc=9)"
Then further expanding the message i am getting the below message
" Error: Server '?' unknown
Tue Mar 02 11:51:05 2010
Release 710
Component NI (Network Interface), Version 39 rc =-3 , Detail NiErrSet. "
Can you please help me out in accessing the servers.
Regards
Vikram

Check OSS Note : 882741
Summary
Symptom
Some users cannot longer connect SAP GUI to any SAP systems e.g. via SAP Logon, SAPShortcut etc. although they have not made any update to either SAP GUI or SAP system. The attempt to connect to the SAP system ends with error messages like this: "Logon balancing error: could not connect to message server (rc=9)", "service sapmsXXX unknown" or "service sapdp## unknown".
The detailed error information is as follows:
    Error: service 'sap...' unknown
    Component NI (network interface), ...
    rc = -3, module ninti.c, line 463
    Detail NiPGetServByName: service 'sap...' not found
    System Call getservbyname
Other terms
service sapmsXXX unknown,logon balancing,service sapdp## not found error,etc/services,drivers\etc\services,getservbyname, sapdpxx
MSN Messenger 7.5,Connection Troubleshooter
Reason and Prerequisites
The reason for this malfunction is, that the datatype of the registry value HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\DatabasePath
was changed from REG_EXPAND_SZ to REG_SZ.
The following programs are currently known to cause this registry change:
Starting MSN Messenger 7.5 "Connection Troubleshooter" (Build 7.5.0299).
Installation of MSN Messenger 7.0 or MSN Messenger 7.5 with the option automatic scanning and configuration of ports.
This modification prevents the expansion of environment variables in the value of the parameter. Therefore,
      %SystemRoot%\system32\drivers\etc
is not translated to
   c:\windows\system32\drivers\etc
and the services database is not found by the API function getservbyname().
If you have checked the datatype of registry value DatabasePath and it is REG_EXPAND_SZ, apply SAP Note 52959 to check the appropriate settings in the services file.
Solution
Start the registry editor and rename the registry value HKLM\System\CurrentControlSet\Services\TCPIP\Parameters\DatabasePath
Create an Expandable-String Value (REG_EXPAND_SZ) with the same name and value.
If more PCs are affected, you can export the correct value to a .reg file and import the .reg to other PCs.
If you have the same problem although you have not installed Microsoft MSN Messenger 7.5, create a customer message, collect the following information and attach it to the message according to note 541726 or upload it to sapservX (see note 40024):
Scan your workstations for spyware and viruses with up-to-date virus definitions. If you already did that what was the result ?
What software has been installed recently ? (client software, Firewall)
Create a registry export of the following key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstallon the affected and the unaffected PC respectively and attach the two .reg files to the customer message.
Are the users on the affected workstations logged on with administrative credentials (local administrator ) ?
Create an MPS Report Networking and Setup Perf of an affected workstation so that we can check if they use an software in common.
You can download the Networking MPS Reporting Tool at:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_Network.exe
You can find a short description about the features of the tool at:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_Network_Readme.txt
The Setup Perf MPS Reporting Tool is located at:
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_SETUPPerf.EXE
Run this report too on identically configured workstations, which are not affected.
If you have already changed back the DatabasePath parameter and if after a while the value was switched back to REG_SZ perform the following steps to help us to identify the reason for this problem:
Switch the datatype back to REG_EXPAND_SZ
Download Regmon from http://www.sysinternals.com on the affected machines
Enable auditing on the affected clients
Modify the settings of the eventlog so that no important entry is deleted!
Open Regedit and highlight HKLM\System\CCS\Services\TCPIP\Parameters
Right-click on "Parameters" and choos "Permissions" and click "Advanced".
Choose "Auditing" and "Add".
Add "Everyone" and select "this key only" under "Apply onto".
Check the boxes "Set Value" and "Delete" and click "OK".
Apply these settings
Start Regmon and apply the correct filter settings:
Press the "magnifying glass" button to stop the monitoring.
Press the rubber button to delete all logged entries.
Go to "Options Filter/Highlight".
Copy the following value to the include field: tcpip\parameters\databasepath and click "Apply".
Start Regmon by pressing the magnifying glass button
Verify that logging starts when you double-click the TCPIP Key in regedit!
If the datatype will be changed again, provide us the output of the monitoring tools.
Solution provided by Microsoft
This issue is said to be fixed as of build 7.5.0311 of MSN messenger.

Sun Messaging Server - Filter based on Message Type

Hi,
Can I do the filtering based on the message type like Voice mail, text mail.. ?
and also can I filter the messages based on the user?

sunstore wrote:
I am looking at filtering more so at the IMAP Level. I would like to only provide certain messages to clients using IMAP using Server Side filters based on message headers. There are no apis/interfaces to "filter" IMAP operations.
Please let me know if this possible. Also i would like to restrict IMAP access to certain users only. Is that possible ? You can restrict IMAP access by using the mailAllowedServiceAccess: attribute:
http://docs.sun.com/app/docs/doc/819-4437/6n6jckqu5?a=view
Regards,
Shane.

Messaging Server: Using UBE feature to filter email bodies or enclosures

Using the UBE feature in Messaging Server to filter email bodies or enclosures

Messaging Server has a feature for filtering unsolicted bulk email(UBE) based
on the envelope information (e.g., the sender's host name ). When the
Parse Headers option is enabled,
filtering by header information (e.g., the subject line of the email) is
performed as well.

The UBE feature is a plug-in that is designed to work with structured header
lines. However, the application of this feature to email bodies is limited.
To filter email bodies, the RUN
action can be used to send a selected
email to an external program, such as VirusScan.exe
. For more information on the
RUN action, see the Netscape
Messaging Server 3.5 Administrator's Guide at 

http://docs.iplanet.com/docs/manuals/messaging/nms35/ag/ch5.htm#actions
RUN 

Argument: 
A command line to execute.

Description: 
The RUN action provides
a means of extending the filtering actions of the UBE filter by running another
program. The program must be in the postoffice (spool) directory for security
reasons. After executing the program, the UBE filter pipes the header and the
body of the email to the program for processing. In addition, you can use the
special field name $& in
subsequent filters to match the return value of the program. For example, 

Subject "May contain a virus" RUN "VirusScan.exe"
$& "1" REJECT "This had a virus"

If there is an email with the subject line "May contain a virus," the filter
will run the virus program VirusScan.exe
and send the entire email to this
program. If the return value from the virus program is "1," then the filter
will reject the email with the reason "This had a virus
Several customers have reported problems with the UBE feature failing to
filter emails using the Content-Type
or Content-Disposition
lines. The reason why the UBE feature
fails with these lines is because they are header style lines that appear in
the email bodies as part of the MIME formatted body. The UBE feature does not
filter emails using these header lines, as it checks only the envelope and
header fields. To target the Content-Type
or Content-Disposition
lines, use the RUN
action with a reference to an
external program. The following lines are examples of header style lines that
can be targetted with a RUN
UBE command: 

Content-Type: application/octet-stream;^M
name="LOVE-LETTER-FOR-YOU.TXT.vbs"^M
Content-Transfer-Encoding: quoted-printable^M
Content-Disposition: attachment;^M
filename="LOVE-LETTER-FOR-YOU.TXT.vbs"^M

Please note: 

Messaging Server 4.0 does not support the RUN
action in the implementation of
the UBE feature. This change is also documented in the release notes for all
subsequent releases of Messaging Server.

For more information on using UBE filters, please see technote 20000506-1,
"I Love You" Virus, article 4355.

RUN is also not available in NMS 4.15 or any NMS 4.x version.
You can however integrate a virus scanner into iMS 5.1 via the conversion channel.
If upgrading is not an option you should consider using a virus scanner that masquerades as a smtp server and forwards scanned messages to the real server.
-Chris

Messaging Server 5.2

Hi again,
Is there a way to do failover for messaging server 5.2 to another ldap?
mail1 --> ldap1 (default)
when ldap1 down
mail1 --> ldap2
Both ldap1 and ldap2 are on different servers. And running MMR for o=Internet, o=pab, o=user suffixes.
Any help would greatly be appreciated. Thanks.

I posted this a while ago, but can't locate it anymore since Sun have 'tweaked' these forums, maybe it's archived !
It discusses how I set up failover for both user and config. trees in ldap. I used mult-master replic. The config. tree failover I found from reading about Netscape Directory Server V6.0 (now owned by Redhat) - See http://www.redhat.com/docs/manuals/dir-server/install/upgrade.htm#17635
There is also mentions to this PTA plugin in relevant directory docs on http://docs.sun.com. So you can have a good read.
Also point 7. in info below describes this.
Hi,
To successfully have a 'low cost' failover iDS5/iMS5 scenerio, you need to do a number of things. Or if you have a wad of cash use Vertias cluster (HA iplanet agents), etc. Directory server proxies (iDAR) :(
Currently I'm using a 'low cost' failover technique.
None of what I'm about to describe is in the SunONE doco. for iMS.
I have tested this in the Lab, all works, it's now in production. Before you do anything, test in the lab first, so you feel comfortable with the setups.
OK my scenerio.
Primary LDAP = ldap-a
Secondary LDAP = ldap-b
Mailserver = mta1
iDS5 = iDS5.1p1
iMS5 = iMS5.2p1
1. Install iDS5 on ldap-a. Acts a User dir. and Config dir. server.
2. Prep. ldap-a for iMS5 install (run ims_dssetup.pl).
     - YES to schema files/indices
3. Install iMS5 on mta1, using ldap-a as User and Config dir. server.
     - I have iMS5 configured in Direct LDAP mode.
4. Install iDS5 on ldap-b, use ldap-b as User and ldap-a as Config dir. server.
     - No need populate the User tree on ldap-b (ie. example users from install)
     - MUST USE ldap-a as config server, as you will be replicating this tree.
if not you will not be able to access the admin server, as you stated.
5. Also run ims_dssetup.pl on ldap-b.
     - YES to schema files/indices
6. Setup multi-master replication between ldap-a and ldap-b.
     - See Admin Guide, have a good read, needs correct setup !
     - This allows read/write, thus seamless to email user for password
     changing, PAB writes...if LDAP has failed over.
     - Replicate all suffices
          o=isp           (User dir.)
          o=internet (DC tree)
          o=pab     (PAB tree)
          o=NetscapeRoot     (Config. dir)
     - Init consumer(ldap-b) from ldap-a for all suffices.
Note: Only problem with multi-master is uniqueness plugins, (if using) it's no problem aslong as you use ldap-a as master. See iDS Admin guide.
7. Now ldap-b requires a change to allow iMS5 to allow writes to o=NetscapeRoot in the event of failover. Otherwise the error message "ldap server unavailable, no configuration server, using locally cached values...whatever blah blah !
Managing Console Fail Over
If you have a multi-master installation with o=NetscapeRoot replicated between your two masters, ldap-a and ldap-b, you can modify the console on the second server (ldap-b) so that it uses ldap-b's instance instead of ldap-a's. (By default, writes with ldap-b's console would be made to ldap-a then replicated over.)
To accomplish this, you must:
Shut down the Administration Server and Directory Server.
Change these files to reflect ldap-b's values:
'serverRoot'/userdb/dbswitch.conf:
directory default ldap://ldap-b:389/o%3DNetscapeRoot
'serverRoot'/admin-serv/config/adm.conf:
ldapHost: ldap-b
ldapPort: 389
'serverRoot'/shared/config/dbswitch.conf:
directory default ldap://ldap-b:389/o%3DNetscapeRoot
'serverRoot'/slapd-serverID/config/dse.ldif:
nsslapd-pluginarg0: ldap://ldap-b:389/o%3DnetscapeRoot
Note: assuming your LDAP TCP port is 389
Turn off the pass through authentication (PTA) plug-in on ldap-b by editing its dse.ldif file.
In a text editor, open the 'serverRoot'/slapd-serverID/config/dse.ldif file.
Locate the entry for the the PTA plug-in: dn: cn=Pass Through Authentication,cn=plugins,cn=config
Change nsslapd-pluginEnabled: on to nsslapd-pluginEnabled: off.
Restart the Directory Server and Administration Server.
8. Now on mta1, using configutil, set options to these values
**a. local.ldaphost = "ldap-a ldap-b"
          - Required to use both servers as Config dir. servers,
in the event of failover, config. is taken from ldap-b.
     b. local.ugldaphost = "ldap-a ldap-b"
          - Required to use both servers for User dir. lookups in event of failover.
c. local.service.pab = "ldap-a ldap-b"
- Required to use both servers for PAB lookup/additions in the event of failover.
     ** To make config dir. failover, shutdown Admin server. and change,
'serverroot'/shared/config/dbswith.conf:
directory default ldap://ldap-a ldap-b:389/o%3DNetscapeRoot
     Restart Admin server.
OK that's all there is too it.
Now test everything, failover LDAP, test logins for email POP/Webmail, IMAP if used.
Test email connections (ie. inbound/outbound email conns)
Note:
Whatever LDAP server fails, iMS5 will continue to use other LDAP server, even when failed LDAP server comes online.
Either stop/start iDS5 on current LDAP server or stop/start iMS5, but not really necessary, depending on your environment, your call !
.....Well it worked for me !
Good luck ;)

How can a remote jms receiver detect loss of connection to Messaging server

Plan:
Messaging server (like JbossMQ /SonicMQ) is hosted on one machine.
A JMS receiver (MDB/core java program) on another machine receives messages from the messaging server.
Secnario:
The JMS receiver is now continuously listening or occasionally reading messages from a certain queue of the server using a JMS connection.
Now the messaging server has this receiver in its list of receivers for that particular queue.
For some reason the messaging server is down and then restarted.
The JMS connection of the receiver is now invalid.
When the messaging servers comes up again its list of receivers is empty.
Required Solution:
Can you please help me on how the JMS receiver can detect the above scenario and re-establish the connetion to the messaging server, the next time the server is up.
Observations:
When I create a message consumer or queue receiver in a j2se program, and take messages from JbossMQ I have some additional threads running on my JVM. These threads are not directly created by the program and servers only for receiving messages. One of these threads is catching an exception and printing a stack trace when it detects that the connection is lost. This will also result in the closing of JMS connection. The problem is that the exception is not thrown for the programmer to catch and handle it at some level. I also tried ExceptionListener and waited for ping interval. Is there a concept of receiver listening to the periodic heart beat of the server. Please give me guidance, solutions or corrections.
For comments on this, Thanks in advance

Hi Leendert,
do you want to use the JMS API directly? In this case you have to create the connection factory on system X. From system Y, you access the JNDI on system X and look up the connection factory. Since you are accessing the JNDI on system X from outside, you need to set some properties to create the InitialContext:
 Properties env = new Properties();
 env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
 env.put(Context.PROVIDER_URL, <system X>:<p4 port>); // replace with your settings
 env.put(Context.SECURITY_PRINCIPAL, <user name>); // replace with your settings
 env.put(Context.SECURITY_CREDENTIALS, <password>); // replace with your settings
 naming = new InitialContext(env);
Hope that helps.
Regards,
Sabine

Messaging Server 4.15 Plug-in API

Similar Messages

Maybe you are looking for