JMS Proxy Service !

Hi I have a scenario --
1. Pandox System(queue) ------> OSB [ ProxyService]-------->Seibel System(queue)
. Is the above scenario possible in OSB ? If yes , then how ?
. Should I go for JMS Bridge ? No ? Yes ? Why?
Note: What would be the end point URIs in the Proxy Service if the systems are non-weblogic like Pandox and Seibel ? Will it require any extra configuration any where in OSB ?

OSB can interface with JMS/MQs.
You can configure your proxy service/business service JMS URI of the pattern if using JMS
jms://localhost:port/QCFJNDI/QJNDI
For MQ you can use the MQ transport or create Foreign JMS servers depending on your version of OSB.
Refer OSB user guide for further details on MQ transport etc.

Similar Messages

Report and Alert don't executed in the error handler with a JMS proxy service

Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.

Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

OSB -11g - Calling JMS Proxy Service in a stage

Hi,
When we createa JMS based proxy service, the proxy service keeps on polling the JMS Queue for any new messages arriving in the queue. But I do not want the proxy service to keep on polling the Queue. Instead I want to call the JMS Proxy Service in any stage (of any other Proxy Service) using a service callout. It means that I do not want the Queue to be polled always, instead the queue should be polled only when this JMS Proxy Service is invoked.
Is it possible to do? If so, how?
Thanks,
Sanjay

Hi Anuj,
Following is my requirement:
The producer wants to interact with us using Web Services. The input payload has some more values (username and password) apart from the HL7 data (base64 encoded) itself. I have to receive the input payload, authenticate the call and convert the HL7 encoded message into an XML and send it to the consumer.
What have I done till now:
1) I have created two Proxy Services PS1 and PS2
2) Proxy Service (PS1) will be invoked by the producer.
3) Then I get the username, password and data from the payload
4) Populate the username and password in the SOAP Header and HL7 data in SOAP Body
5) Call PS2 from PS1
6) In PS2 I have configured Message Level Security to authenticate with the username and password
7) After authentication I make a Java Callout to decode the base64 encoded HL7 data
8) I now have written my own HL7 sender (Java code) which wraps the decoded HL7 data with MLLP requirements and then send it to the B2B server using a Socket (TCP connection). I do a Java Callout to this Java class.
9) In B2B I have configured a RTP (Remote Trading Partner) which has a MLLP channel.
10) I created a ADT message document and a ACK document
11) I created two agreements between HTP and RTP (one agreement receives the HL7 data from the TRP using MLLP and another which sends the ACK to the RTP using MLLP channel)
12) In the receiveing agreement I have configured a JMS channel (on the HTP side) becuase of which B2B receives the HL7 Pipe delimited data and translates it and then pushes the XML data into the JMS queue (which needs to be transformed to producer XML)
13) I have also configured a JMS channel for the RTP which I am using in second agreement to get the acknowledgement. Because of this the ACK is placed in a JMS queue.
I need to poll this JMS queue in order to send the ACK back to the producer (which I have to do in the response pipeline of PS2). Hence I wanted to pop the message from the JMS queue in the response pipeline and then send that message.
Please advice if my approach is correct.
Thanks,
Sanjay
Edited by: Sanjay Bharatiya on 17-Mar-2011 12:06 PM

The JMS proxy service unable to route to another Proxy Service

Hello,
I have a JMS proxy service. Inside its pipeline, I am routing to another Proxy Service of Service Type "Messaging", protocol: "Local" & Request Message Type: "XML"
It's printing the message correctly from inside the routing node in the pipeline of JMS proxy. However, it's not invoking the Proxy Service that I am routing to, since I am not seeing the log message that I am trying to print from inside the pipeline of Local Proxy. Could someone please point out the error in my configuration?
Any help will be greatly appreciated.
Thanks much,
Mamta Kansal

OSB/ALSB use the SOA Suite forum
SOA Suite

How to make a JMS Proxy Service Subscriber act as a synchronous service

I am trying to find the correct OSB pattern/configuration to support the following.
Use case:
Multiple messages put onto a JMS topic. The Java Web Service invoked by the Proxy Service subscriber should only ever have one instance active at a time so that it processes messages syncronously.
Current OSB Configuration:
JMS Topic -> ProxyServiceA -> BusinessServiceA (Java Synchronous Web Service)
-> ProxyServiceB -> BusinessServiceB (BPEL Synchronous Web Service)
Work Manager configured on ProxyServiceA with maxThreadCount = 1 and minThreadCount = 1
Issue:
Multiple instances of BusinessServiceA are active at the same time with the settings above. I am unable to make ProxyServiceA act as a synchronous process, so that it will not return until BusinessServiceA has completed.

JMS Topic -> ProxyServiceA -> BusinessServiceA (Java Synchronous Web Service)-> ProxyServiceB -> BusinessServiceB (BPEL Synchronous Web Service)
If I remember correct there were some issue with work-manager being configured in proxy is not used. Engineering has fixed that issue in Oracle Service Bus (11.1.1.3.0). You might want to check with support to get the requisite patch for your version.
You requirement for synchronous process can be achieved by two ways
Option1) Configure BusinessServiceA with Throttle Q with Maximum Concurrency 1 http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/throttling.html
Multiple instances of BusinessServiceA are active at the same time with the settings above. I am unable to make ProxyServiceA act as a synchronous process, so that it will not return until BusinessServiceA has completed.Does BusinessServiceA (Java Synchronous Web Service) return response? Is it invoking the ProxyServiceB via HTTP?
Manoj

How to forward message to two different queue using jms proxy service

Hi all,
In my project I need to listen to one jms queue then forward the messages to two different queue.
Now I already made one proxy for listening to the queue then pass it to another queue using business service, It works.
But how to forward the messages to two different queue in same flow process using one proxy and bs??
or any other way?
Really thanks in advance.
Regards,
Kahlil

Hi,
I have a MQ queue and i created a Proxy to listen to the queue , but i dont see any activity in OSB logs ..how do i knw if OSB proxy is polling that MQ ( mq is the transport protocol that i am using ) .
Thanks
Prarthana.

How to specify the JMS Client ID in Proxy Service of OSB 11.1.1.5 version ?

Hi All,
I am looking for an option to set the JMS clientID for a JMS Proxy services in OSB. Can this feature available in OSB 11.1.1.5 version?
Thank you,
Ram.

These links will helpful for you.
http://jdevadf.oracle.com/adf-richclient-demo/docs/tagdoc/af_train.html
http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e12419/tagdoc/af_train.html

Consume JMS Unit-Of-Work message through OSB proxy service

Hi,
Anyone know how to consume a JMS Unit-Of-Work (UOW) message using an OSB Proxy Service of JMS type?
I can submit a unit-of-work JMS message (which consists of multiple constituent messages) using an OSB proxy & business service combination and setting the UOW transport headers appropriately. I can also separately produce and consume Java objects via a JMS queue where the consumption is done via OSB proxy (of java request message type), but these aren't UOW messages.
Apparently as soon as it is a UOW message then the message consumed is an ObjectMessage ArrayList and one has to use the "Java" request message type for the JMS consumer proxy, but I'm unsure of how to create the concurrent client jar to use it in the same proxy service's JMS transport configuration in order to output the ObjectMessage ArrayList (UOW message).
Ideally I'd like to consume a single UOW XML message via an OSB JMS proxy service.
Any pointers would be appreciated.
R

Finally got this working!!
For posterity: Needed to insert Java Object JMS messages on the OSB JMS producer (Business Service) side with correct UOW jms transport header set in route node. Then consume the Unit-Of-Work message on the other side via jms proxy service with "java" request message type, with appropriate jar containing the Object class as the "Client jar" in the JMS Transport configuration. In the same JMS consumer proxy I had to do a java callout, passing the contents of $body, using java.util.ArrayList and javax.jms.ObjectMessage, as input into a method (.. decodeJavaMessage(ArrayList<ObjectMessage> ...)). In this java callout class you can get to each individual ObjectMessage via typecasting the get() method on the Arraylist to (ObjectMessage) and then just typecast the getObject() on this Objectmessage into your original Java Class (same as what you inserted onto queue originally).
Hope this saves someone some time in future!

JMS Biz & Proxy Services Using OSB & SSL

We have a potential requirement being enforced upon us which states that our communication to another system using a JMS proxy service should be using SSL.
Has anyone done this before using OSB?
There is a "Use SSL" tick box on the proxy and business services, but I think this is purely for authentication and not transport - but I could be wrong as its not an area I know that much about.
We're pushing for an IPSEC VPN link as that makes much more sense, but in the meantime I thought I'd ask if anyone had done any JMS + SSL work using OSB.
Thanks,
Pete

Manoj, Thanks for your reply.
Actually the other system is OSB!!
It's a government system we're talking to but in the interests of open-ness, we cannot use OSB->OSB out of the box interfaces such as SAF etc, as that isn't an open enough interface and users of the interface who don't have OSB may be disadvantaged! Something like that anyway! SAF would be a perfect option for this interface, but .....
What we've been so far is that all communication via JMS must be SSL based. But - t3s is not supported on this interface, so the SSL negotiation must be handled by a hardware device or something else.
We think we've found BigIP load balancers do the job, but that's a large cost as we don't have those in our current infrastructure.
We don't have much SSL communication apart from https, so I don't have a whole lot of experience with it and I just wondered if there was any OSB feature I'm missing, or something you can do in plan java code to get JMS communicating via SSL.
Pete
ps:A standard IPSEC VPN would do the job too, which we're going to try to push for, then, you just use the jms:// url to an address and the security is via the VPN.

Stuck Thread - JMS Business proxy Service (ALSB 2.5)

Hi All,
We are having a jms proxy service which uses a JMS Business Service to send messages to a jms queue on weblogic 8.1 sp6. The alsb domain runs on weblogic 9.2.The jms proxy service is made single threaded by configuring a suitable work manager.
Now and then, we get a stuck thread issue in production and the proxy service stops consuming the messaging off the jms queue in wls 9.2. These are the errors in the logs:
<[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1235437298516> <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "695" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@5321caf", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-70 "[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, waiting, priority=1, DAEMON> {
-- Waiting for notification on: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
jrockit.vm.Threads.waitForSignal(Native Method)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Native Method)
weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:73)
^-- Lock released while waiting: weblogic.rjvm.ResponseImpl@51961a5[fat lock]
weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:100)
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
weblogic.jms.dispatcher.DispatcherInteropAdapter.dispatchSyncTranFuture(DispatcherInteropAdapter.java:80)
weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:230)
weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:51)
weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1047)
weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
weblogic.jms.client.JMSProducer.send(JMSProducer.java:352)
weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:1009)
weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.java:157)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:795)
com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:500)
com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:612)
jrockit.reflect.CompiledMethodInvoker.invoke0(Unknown Source)
jrockit.reflect.CompiledMethodInvoker.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
com.bea.wli.sb.transports.Util$1.invoke(Util.java:241)
$Proxy39.sendMessageAsync(Unknown Source)
com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:137)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:437)
com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:328)
com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContextImpl.java:503)
com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextImpl.java:415)
stages.publish.runtime.PublishRuntimeStep.processMessage(PublishRuntimeStep.java:106)
com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:327)
com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:100)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:73)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:47)
com.bea.wli.sb.pipeline.Node.processMessage(Node.java:57)
com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:771)
com.bea.wli.sb.pipeline.Router.processMessage(Router.java:141)
com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:75)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:646)
com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:645)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:627)
com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:264)
com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:108)
weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:292)
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
weblogic.jms.client.JMSSession.execute(JMSSession.java:4012)
weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
jrockit.vm.RNI.c2java(Native Method)
Any one know the root cause of this issue or ways to prevent this?
Also Is there a way to make the proxy service to reconsume messages off the queue without a server restart?
Thanks,
Atheek

Hi atheek, did you find the solution??
I already got the same/identic issue, do you mind giving me an aid?
Really thanks
Regards,
Mr.K

OSB 1031: proxy service and publishing JMS messages with no duplicates

Hi all,
we have a Web Service proxy that publishes messages into a JMS queue. The queue is persistent and the related connection factory is XA enabled.
The proxy does the call to the JMS business service from a route node.
If a failure occurrs after the publishing returns successfully, the caller receives back an error and it will try again to call the web service proxy.
As the message has been published successfully and was not rollbacked by the proxy, the second call could put on the JMS queue a duplicate message.
As far as we know only with JMS proxy service, OSB starts a transaction within the pipeline or are we wrong ?
What do you suggest in order to avoid such a scenario described above ?
Thanks and regards
ferp

Try this link to depict the behavior
http://allthingsmdw.blogspot.com.au/2012/09/osb-service-callouts-and-oql-part-1.html

JMS Distributed Destinations as proxy service endpoints

We have a cluster of 2 ALSB servers with a proxy service deployed
listening on a JMS queue which is a distributed destination (DD) on a
WLS 8.1 system.
The JMS DD is spread across 4 JMS servers and 4 JVM's.
When ALSB starts up - we only get consumers on 2 of the 4 DD members,
which makes sense as a JMS proxy service is essentially an MDB, and this
is normal MDB/distributed destination behaviour - it will bind to the
queue member where it first makes the connection to the JVM.
How do I make sure my messages are consumed from all 4 DD queue members?
There is a JMS option to forward messages to queues with consumers if no
consumers exist - is that the way to do it?
Someone must have come across this before and I'd be grateful for any
advice.
Also - how do you reduce the consumers on the JMS queue - seems to
default to 16. Perhaps you don't.
Thanks,
Pete

Meghan Pietila wrote:
Update: I see your exchange with Tom over on the JMS forum, Pete. We just switched everything to WLS 9.2, so maybe the ALSB internal extension will work for us. It's not working by default, so possibly it's something that must be activated... I'll follow up with BEA.
http://forums.bea.com/thread.jspa?threadID=570001317
I'd still like to hear what you end up working with, if you don't mind sharing once it's running. :)
MeghanI only have 8.1 as an option - a JMS proxy service is essentially an
MDB, and if you deploy an MDB in the same way, it will only bind to a
single destination, so it's actually behaving as I would expect.
The forward delay on the queue probably won't be an issue for us, as
we're not talking about high volumes and large messages, but for some
sites there will be alot of moving around queues, access jms filestore
etc which you could do without.
I reckon the trick is (as Tom mentioned) to bind to individual
distributed queue members from the proxy service somehow.
I'll let you know what I find out.
Pete

OSB 11g acting as a JMS Proxy

I was hoping that someone can clear my understanding of OSB and how it interacts with JMS.
I created a JMS server, connection and topic in WLS. It works great. I am able to subscribe and publish from a java client and from an OSB business service.
Our use case is to use OSB as a "front end" to JMS if you will. We want JMS clients to be able to connect to OSB and subscribe to our JMS topic (durable). Is it possible to subscribe to a proxy service from a JMS client? How do I do it?
The next thing we are going to try to do is have an OSB process listen to our JMS topic and invoke a web service when a new message is published. Any guides on this?
Thanks so much,
Sam

We want JMS clients to be able to connect to OSB and subscribe to our JMS topic (durable). Is it possible to subscribe to a proxy service from a JMS client? How do I do it?I don't think subscribing to a proxy service is possible. Instead create a separate queue (or any other storage), for your client application and let OSB pull the message from source queue and pass it to target storage (may be another JMS queue)
The next thing we are going to try to do is have an OSB process listen to our JMS topic and invoke a web service when a new message is published. Any guides on this?This approach is quite similar to what I mentioned above. Just create a JMS proxy service to let it consume messages from topic and create a Business Service (WSDL based web-service) to invoke the target web-service. In the message flow of JMS proxy you may have transformation if required, and then route the message to business service which will eventually deliver the message to target web-service.
Regards,
Anuj

OSB Proxy Service - ignore XML processing instructions (PIs)

Hello,
I've got a proxy service in OSB that takes any XML, transforms it, and passes it through to a business service. i.e. it just has a simple routing node containing something like:
Route to [ BusinessServiceDB ] invoking [ merge ]
Replace [ node contents ] of [ undefined XPath ] in [ body ] with [ XQuery Resource... ]
This works fine until the XML contains a processing instruction other than the standard XML version one; <?XML...?>. So if the first line (or first line after the XML version, if present) contains a PI (e.g. <?some-app-specific-instruction?>), then the proxy service passes nothing through to the Business Service.
Well, I guess it assumes that the <?some-app-specific-instruction?> is the entire node contents, and so effectively passes through nothing that matches in the XQuery code...
Is there a setting or easy way to make OSB globally ignore PIs? Or will I have to do something with the Replace, e.g. define the XPath or variable bindings differently?
Cheers...

Thanks, I will do that...once I've found out what our support ID is.
The problem is easily repeatable in less than five minutes - all you have to do is create an 'Any XML' JMS proxy service (with all settings as defauts), and just have an empty route node in the message flow.
Then all you do is try the test console with something like "<blah>test</blah>" as the payload; on the results you will see the correct XML inside the soapenv body when you expand: receiving request > Initial Message Context > $body. Then repeat the test with"<?something?><blah>test</blah>", which will only pass through the soapenv:Body tag with no contents.
I presume this is not expected behaviour? i.e. OSB isn't meant to try the processing instruction, then pass through the results of that? I can't imagine it would...
Anyway, as I say, I will raise the support request...but if anyone that is on a version above 10.3.1 has time to quickly run this test and let me know the results, I'd be really grateful.

ALSB Proxy services deployment management

Hi all,
I have a problem now.
We have many proxies services running in a ALSB domain.
Some of them need to transfer hundreds MB XML data very frequently. They are listening to a JMS queue. And when they are working, they will cause the whole system too heavy-loaded to work.
So we want to add a new server into this ALSB domain to run the data transfer proxy services.
Because the data transfer proxy services have too much dependencies to separate, our thought is to deploy the all the projects to the new server and control the data transfer proxies only run on the new server.
Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?
Thanks in advance.
Garriot Zhang

Is it possible? Can I specify some JMS proxy services only running on server1 and other proxy services running on server2 (server1 and server2 are in the same domain) in ALSB?No. When a proxy is deployed it gets deployed to all servers. OSB does not give explicit control on which server a proxy should be deployed.
Manoj

JMS Proxy Service !

Similar Messages

Maybe you are looking for