Port Knocking client for Symbian?

I was wondering if a port knocking client existed for Symbian (specifically the N8)?
http://en.wikipedia.org/wiki/Port_knocking
Thanks

not that i'm aware of. and i would say that the chances are pretty slim. these kinds of applications are rare on mobiles, even client side, given that their IPs are rarely routable.
what are you ultimately trying to achieve. maybe that is a better approach.
There's no dignity in begging for kudos. Do it for the karma.

Similar Messages

Native Client for Symbian Mobiles

I've a Sony-ericsson 910i with Symbian and the proprietary as well as
Opera browser.
I'm looking for a native client to use on this so that I may access our
SAP system. I've seen some reference to a client being available for the
Nokia 9210 (which runs Symbian) but can't seem to find any more info or
the download for this.

Jason Roesler wrote:
II am interested to know,
Is there an native client for enterprise eddition or enterprise 3 for
Solaris x86?
thanks
Hi.
There should be in the upcoming 4.1 release of SGD EE.
Native Clients should be available for Windows, Linux (Intel x86), Sparc
Solaris, x86 Solaris, MAC OS/X.
Best,
Rob
Roberto Zini - r.zini<@AT@>strhold.it
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

SIP Client for Symbian (Nokia N91)

Anybody have a SIP Client for Nokia N91 (Symbian OS)or knows dates of releases, links, any thing?
Thanks
Juan

Did you get a SIP client for the N91? if so where from.

Swype for Symbian ^3, Anna, Belle, Belle Refresh i...

Swype for Symbian ^3, Anna, Belle, Belle Refresh is EXPIRED. What should I do?
Swype is expired irrespective of the firmware on your device, please help.
Symbian connected me to the world, to my dreams.. Thank-you Nokia

Symbian^3 phones are not compatible with SymRDP software.
You may see that these phones are NOT included in Compatible Devices List for SymRDP software.
SymRDP will close automatically on most non-compatible phones.
There is no VNC nor TeamViewer remote access for Symbian^3.
You may check if anyone is interesting in developing software for Symbian^3. You may check www.rdmplus.com as they used to develop some Java based Remote Access clients for Symbian.
Most likely, the bottom line is – if you need Remote Desktop access, then you should not use Symbian^3 phones and use some real smartphones instead as all of them have support for RDP and VPN access and many have support for access via SMB protocol as well (file sharing).

Java Socket - port knocking

Hi
I'm new here sorry if this subject was already discusssed. I was trying to find answer without result.
I have to write simle client for port knocking technique in java, and i have little problem
Port knocking daemon works fine (easy just read firewall logs) but client i sending many packets instead of one... When server is behind the firewall
To "knock" to the server I'm using quite simle command:
Socket S = new Socket(ip,port);
Dou you have any idea how to make it work. I need this client to knock only once..
Cheers,
PP5585

Thanks:) So the only way is not to allow my port knocking to have knocks kombination like:
113455 or 22334455
And if there will be knock to the same port again just ignore it.
Cheers,
Piotr

How do you configure the set of port to use for FTP passive data connection

I was able to start the ftp server xml db and connect to it locally. When I tried to connect to it from home, I was able to log in but when i do a "get" command the sessions hangs. I also tried passive mode and do a "get" command and it gives me a connection refused error. I am using the default port 2100. I think this might be a firewall issue with the data connection port. I am not sure which range of ports to open for the passive ftp connection on the server side or where to go and set them for for the ftp server to use? Or this issue might not be firewall related??? Any thoughts. Thanks.

This is a typical problem with VPN/Firewall software and FTP on ports other than 21.
When you open the FTP data connection the FTP Server identifies which port the data will be sent on using the PORT command which is sent on the command port (typically 21 with a normal FTP server, 2100 by default with XDB). THe client then opens that PORT to accept the data (file, output of an ls etc).
As I understand it most VPN/Firewall are configured to monitor 21 for 'PORT' requests. They then understand to allow connection on the PORT number passed on the command PORT. Hence with Port 21 firewall / VPN software is not a problem. However since the XDB command PORT is something other than 21 they do not see / honour the PORT commands from the server and hence the client cannot open the data connection on the specified PORT
As to how to solve it, I wish I knew (After 5 years I still can't use XDB FTP from home to a machine in the office once the VPN tunnel is open :( ). I'm sure it's going to be firewall / VPN software specific and may need the VPN servers to be configured.
The best bet would be to run the FTP server on 21...
Add the following line to your listener.ora file
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = hostname) (PORT = 21))
(PROTOCOL_STACK = (PRESENTATION = FTP) (SESSION = RAW)))
and then restart the listener as root
Start the listener as root.
At the operating system prompt, enter tnslsnr with optional command line arguments. The usage is as follows:
tnslsnr [listener_name] [-user user] [-group group]
where:
Table 4-3 tnslsnr Utility Options
Option Description
listener_name
Specify the name of the listener. If omitted, the default name LISTENER will be used.
-user user
Specify the user whose privileges the listener will use when super user (root) privileges are not needed. After performing the privileged operations, the listener will give up root privileges irreversibly.
-group group
Specify the group whose privileges the listener will use when super user (root) group privileges are not needed. After performing the privileged operations, the listener will give up root group privileges irreversibly.
The listener will temporarily switch to the provided user and group immediately after startup. All subsequent operations will be done with the specified user and group privileges, except the system calls necessary to listen on configured endpoints. The listener will revert to super user (root) for a short period of time to listen on reserved addresses, such as TCP ports less than 1024. After the listener starts listening on all of its endpoints configured in listener.ora, it will switch to the specified user and group irreversibly. Therefore, the listener will give up the root privilege that it initially had. In the current release, -user and -group command line arguments only accept user and group identifiers specified in numeric form.
For example, to execute a root listener called mylsnr and have it use privileges of a user identified

IDX1: Port SAPIDS, client 800, RFC destination contain error

hi
i changed the client on xi for idoc to file scenario.
in sm 58 iam getting following error
Transaction IDX1: Port SAPIDS, client 800, RFC destination contain error
regards viju........

VIJENDER SRIRAMOJU,
If you change the client on xi for that scenario, make the corresponding changes
in Idx1.
Also delete the entries from Idx2. (entries in idx2 are read automatically during runtime)
There is a howto on idoc scenario in sdn. Just go through that.
reg,

Problem with DII client for Doc/Literal with non built-in type in WL8.1 Sp2

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Hello,
I have been trying to make this DII client for doc/literal using non built-in type to work for 2 days now.
Any help/input will be greatly appreciated. I have added the code and wsdl below.
BTW this is using the code first approach.
Works perfectly fine with the clientgen generated stubs. But not with DII.
With the stubs, following is the SOAP envelope.
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:getType xmlns:n1="http://www.aeb.com/wlws">
     <n2:id xmlns:n2="java:com.aeb.types">XYS</n2:id>
     <n3:name xmlns:n3="java:com.aeb.types">Name</n3:name>
</n1:getType>
</env:Body>
</env:Envelope>
With DII (using the serializer/deserializer generated by clientgen),
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header/>
<env:Body>
<n1:TestType xmlns:n1="java:com.aeb.types">
     <n1:id>ABC</n1:id>
     <n1:name>Some Name</n1:name>
</n1:TestType>
</env:Body></env:Envelope>
Exception
javax.xml.rpc.soap.SOAPFaultException: Unable to find a matching Operation for this remote invocation
<n1:TestType xmlns:n1="java:com.aeb.types">
<n1:id>ABC</n1:id>
<n1:name>Some Name</n1:name>
</n1:TestType>.
     Please check your operation name.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:313)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:558)
     at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:411)
     at com.amgen.webservice.clients.DocClient.callService(DocClient.java:83)
     at com.amgen.webservice.clients.DocClient.main(DocClient.java:35)
Client
System.setProperty("javax.xml.rpc.ServiceFactory","weblogic.webservice.core.rpc.ServiceFactoryImpl");
System.setProperty("weblogic.webservice.verbose", "true");
String targetNamespace = "http://www.aeb.com/wlws";
ServiceFactory factory = ServiceFactory.newInstance();
QName serviceName = new QName(targetNamespace, "DocWebservice");
QName portName = new QName(targetNamespace, "DocWebservicePort");
QName operationName = new QName(targetNamespace, "getType");
Service service = factory.createService(serviceName);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING);
mapping.register(TestType.class, new QName("java:com.aeb.types","TestType"), new TestTypeCodec(), new TestTypeCodec());
Call call = service.createCall();
call.setOperationName(operationName);
call.setPortTypeName(portName);
call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(Call.OPERATION_STYLE_PROPERTY, "document");
call.addParameter("testType", new QName("java:com.aeb.types","TestType"), TestType.class, ParameterMode.IN);
call.setReturnType(new QName("java:com.aeb.types", "TestType"),TestType.class);
call.setTargetEndpointAddress("http://localhost:7001/wlws/DocWebservice");
TestType type = new TestType();
type.setId("ABC");
type.setName("Some Name");
TestType res = (TestType) call.invoke(new Object[] { type });
System.out.println(res.getName());
TestType.java
package com.aeb.types;
import java.io.Serializable;
public class TestType implements Serializable {
     private String id;
     private String name;
     public String getId() {
          return id;
     public void setId(String id) {
          this.id = id;
     public String getName() {
          return name;
     public void setName(String name) {
          this.name = name;
DocWebservice.java
package com.aeb.webservices;
import com.aeb.types.TestType;
public class DocWebservice {
     public TestType getType(TestType type) {
          System.out.println("In Server....");
          System.out.println("Received : " + type.getName());
          return type;
ServiceGen Ant Task
<servicegen destear="${dist.dir}/wlws.ear" contexturi="wlws">
     <service javaClassComponents="com.aeb.webservices.DocWebservice"
          generateTypes="True"
          targetNamespace="http://www.aeb.com/wlws"
          serviceName="DocWebservice"
          serviceURI="/DocWebservice"
          style="document">
          <client packageName="com.aeb.ws.doc.client" />
     </service>
</servicegen>
WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:tns="http://www.aeb.com/wlws" xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding" xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.aeb.com/wlws">
<types xmlns:tns="http://www.aeb.com/wlws"
xmlns:wsr="http://www.openuri.org/2002/10/soap/reliability/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap12enc="http://www.w3.org/2003/05/soap-encoding"
xmlns:conv="http://www.openuri.org/2002/04/wsdl/conversation/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="http://www.aeb.com/wlws"
xmlns:tp="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="http://www.aeb.com/wlws">
<xsd:import namespace="java:com.aeb.types">
</xsd:import>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getType"
nillable="true">
</xsd:element>
<xsd:element xmlns:tp="java:com.aeb.types"
type="tp:TestType"
name="getTypeResponse"
nillable="true">
</xsd:element>
</xsd:schema>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stns="java:com.aeb.types"
elementFormDefault="qualified"
attributeFormDefault="qualified"
targetNamespace="java:com.aeb.types">
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element type="xsd:string"
name="id"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
<xsd:element type="xsd:string"
name="name"
minOccurs="1"
maxOccurs="1"
nillable="true">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</types>
<message name="getType">
<part xmlns:partns="http://www.aeb.com/wlws"
name="testType"
element="partns:getType">
</part>
</message>
<message name="getTypeResponse">
<part xmlns:partns="http://www.aeb.com/wlws"
name="result"
element="partns:getTypeResponse">
</part>
</message>
<portType name="DocWebservicePort">
<operation name="getType">
<input message="tns:getType">
</input>
<output message="tns:getTypeResponse">
</output>
</operation>
</portType>
<binding type="tns:DocWebservicePort"
name="DocWebservicePort">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http">
</soap:binding>
<operation name="getType">
<soap:operation style="document"
soapAction="">
</soap:operation>
<wsr:reliability persistDuration="60000">
</wsr:reliability>
<input>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</input>
<output>
<soap:body namespace="http://www.aeb.com/wlws"
use="literal">
</soap:body>
</output>
</operation>
</binding>
<service name="DocWebservice">
<port name="DocWebservicePort"
binding="tns:DocWebservicePort">
<soap:address location="http://localhost:7001/wlws/DocWebservice">
</soap:address>
</port>
</service>
</definitions>
Thanks
Aspert

Help me in writing client for this JAX ws Web service

Hi ,
I am unable to write client for my Webservice deployed under glass fish v3 .please help.
package jws;
import javax.jws.WebService;
import javax.jws.WebMethod;
import javax.jws.WebParam;
@WebService(name="CalculatorPortType")
public interface Calculator {
    @WebMethod
    public int add(int value1, int value2);
} package jws;
import javax.jws.WebService;
@WebService(serviceName = "Calculator",
            portName="CalculatorPort",
            endpointInterface = "jws.Calculator")
public class CalculatorService implements Calculator {
    public int add(int value1, int value2)
         System.out.println("Inside web service class ");
        return value1 + value2;
My client which is incomplete :please help
import java.net.URL;
import jws.CalculatorService;
import jws.Calculator;
import javax.xml.ws.Service;
import sun.print.resources.serviceui;
public class Hi {
@WebServiceRef(wsdlLocation=
"http://localhost:8089/Ram/Calculator?wsdl")
CalculatorService service ;
public static void main(String argsp[]) throws Exception
} This is deployed under glassfish v3.

When you just use the JAX-WS standard you do not need any WebLogic related classes to create a client for your web service.
When the web service is deployed the WSDL can be accessed. By using this WSDL you can create your client by using tools
such as wsimport (which comes with a JDK distribution and is located in the JDK_HOME/bin directory)
wsimport -keep -d C:\YOUR_PROJECT\src http://hostname:port/context/SomeWebService?wsdlthe 'keep' option make sure the generated .java files are not thrown away.

RE: Java-based Client for Forte/IIOP

We have deployed an application using JDK 1.1.6,
Swing 1.0.3, Visibroker 3.2, and Forte 3.0.G.2.
We are also using Forte's Java Interoperability
Service.
We have a closely-held client base (i.e. not a
million random yahoos off the internet), so we can
secure a Java port between client and server and
download a fairly significant client. The Java
client is deployed with Sun's JRE (to control the
environment) with the following configuration:
2.6 MB JRE
765 KB Forte.zip
2.0 MB swingall.jar
1.6 MB vbjtools.jar, vbjorb.jar
100 KB application classes
1) The Swing controls don't interoperate well
with the AWT and Symantec widgets, especially in
an internal frame. They paint slowly on top of
each other, move jerkily, and paint before moving
to the programmed coordinates so it looks silly.
100% Swing controls play well with other Swing
controls and are reasonably fast.
2) We used Symantec Cafe 2.5a to paint the
screens, and had some problems with the
setLayout(null) on things like the Swing tab
folder and split panel. Commenting out the line
fixed it, but I'm hoping Cafe 3.0 will fix it (I
have a person installing it but haven't gotten a
report...)
3) The initial search time to turn an IOR file
into a reference is an annoying 10 seconds, and
the first method call takes about 7 seconds, but
after that is less than a tenth of a second.
Haven't done any digging to find out why yet.
4) If we were deploying this as an applet, we
would probably use the IDL IIOP export--when using
the Java Interoperability service, any method call
seems to load the whole 765K across the
line...class by class. Ugly. IDL just gets what
it needs and is smaller.
5) Also, if deploying as an applet, we wouldn't
have to download the JRE or visibroker jar files,
and would only download the swing and Forte IDL
generated classes as needed, so it would be a much
smaller footprint than the 7MB above. (Note:
However, we would be at the mercy of the browser
being used by client.) Different strokes for
different folks...
-DFR
From: [email protected]
Date: Tue, 01 Dec 1998 15:15:18 -0800
Subject: RE: Java-based Client for Forte/IIOP
Sean,
My worry is that Swing, while eloquently designed,
represents an attempt to
write a totally new display system which, at least
in the case of my
project, will run on top of Windows. I really like
the Java (or a Java-like
i.e. J++) language, but I feel safer using the
native MS widgets. It does
not seem that anyone on this forum has used Swing
extensively and can
testify to its stability and performance.
Regards,
David
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

We have deployed an application using JDK 1.1.6,
Swing 1.0.3, Visibroker 3.2, and Forte 3.0.G.2.
We are also using Forte's Java Interoperability
Service.
We have a closely-held client base (i.e. not a
million random yahoos off the internet), so we can
secure a Java port between client and server and
download a fairly significant client. The Java
client is deployed with Sun's JRE (to control the
environment) with the following configuration:
2.6 MB JRE
765 KB Forte.zip
2.0 MB swingall.jar
1.6 MB vbjtools.jar, vbjorb.jar
100 KB application classes
1) The Swing controls don't interoperate well
with the AWT and Symantec widgets, especially in
an internal frame. They paint slowly on top of
each other, move jerkily, and paint before moving
to the programmed coordinates so it looks silly.
100% Swing controls play well with other Swing
controls and are reasonably fast.
2) We used Symantec Cafe 2.5a to paint the
screens, and had some problems with the
setLayout(null) on things like the Swing tab
folder and split panel. Commenting out the line
fixed it, but I'm hoping Cafe 3.0 will fix it (I
have a person installing it but haven't gotten a
report...)
3) The initial search time to turn an IOR file
into a reference is an annoying 10 seconds, and
the first method call takes about 7 seconds, but
after that is less than a tenth of a second.
Haven't done any digging to find out why yet.
4) If we were deploying this as an applet, we
would probably use the IDL IIOP export--when using
the Java Interoperability service, any method call
seems to load the whole 765K across the
line...class by class. Ugly. IDL just gets what
it needs and is smaller.
5) Also, if deploying as an applet, we wouldn't
have to download the JRE or visibroker jar files,
and would only download the swing and Forte IDL
generated classes as needed, so it would be a much
smaller footprint than the 7MB above. (Note:
However, we would be at the mercy of the browser
being used by client.) Different strokes for
different folks...
-DFR
From: [email protected]
Date: Tue, 01 Dec 1998 15:15:18 -0800
Subject: RE: Java-based Client for Forte/IIOP
Sean,
My worry is that Swing, while eloquently designed,
represents an attempt to
write a totally new display system which, at least
in the case of my
project, will run on top of Windows. I really like
the Java (or a Java-like
i.e. J++) language, but I feel safer using the
native MS widgets. It does
not seem that anyone on this forum has used Swing
extensively and can
testify to its stability and performance.
Regards,
David
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Novell Client for Linux 2 beta & VMWare - bridged only?

OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
OpenSUSE is installed as a VMWare Workstation guest using NAT. When attempting to use contextless login, the Novell Client hangs. If you disable contextless login and then browse to the right context, you can login OK.
If you change the virtual NIC from NAT to Bridged, contextless login works fine. If at all possible, we need to use Bridged instead of NAT (long story).
Any idea what could be the problem? From what I can tell, SLP, DA, etc are set correctly, but I could be wrong.
Thanks.

Originally Posted by Thorsten Kampe
* mlazovjp (Mon, 14 Dec 2009 18:56:02 GMT)
> OpenSUSE 11.1 with Novell Client for Linux 2.0 SP2 beta.
>
> OpenSUSE is installed as a VMWare Workstation guest using NAT. When
> attempting to use contextless login, the Novell Client hangs. If you
> disable contextless login and then browse to the right context, you can
> login OK.
>
> If you change the virtual NIC from NAT to Bridged, contextless login
> works fine. If at all possible, we need to use Bridged instead of NAT
> (long story).
>
> Any idea what could be the problem? From what I can tell, SLP, DA, etc
> are set correctly, but I could be wrong.
Use NAT only if you need NAT - otherwise use bridged.
Thorsten
I was afraid that someone was goign to say something like that :)
We use port security hardware on our network, which will disable a port on the switch if it detects multiple MAC addresses on the same port. A virtual machine's bridged networking sets port security off and disables the port, so we have had to resort to NAT for all virtual machines. We can ask for exceptions to be made for a subset of our lab computers, but that is not an ideal solution.
Not only is that extra overhead for us to manage these exceptions, but we will not be able to realize our long-term goal of providing the virtual machine to our students to use on their personal notebooks since we cannot provide them port security exceptions.
I am still having problems grasping the reason that a contextless lookup (via LDAP, I assume) would misbehave while coming from a NATted connection but a bridged connection works fine on the exact same virtual machine. Shouldn't the communication between the VM and the LDAP server work properly either way??

Wired mac using Express as client for Snow base?

Hello All,
Is it possible to plug a non-Airport Mac into the Ethernet port of the Express and essentially use it as a client for an existing older Airport network (Snow base station)?

No. This requires a WDS and the Snow base station doesn't support WDS.

Stand alone client for remote EJB corba error

Regarding problem below, I've checked System env variables
that weblogic server is using for CORBA classes:
javax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
org.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
org.omg.CORBA.ORBClass weblogic.corba.orb.ORB
javax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
But these are server classes and not found in wlclient.jar and wljmsclient.jar. What classes should be used for client? What needs to be set in order to get successful remote RMI/EJB call to weblogic server?
Original post:
I have a stand alone spring client for simple stateless session EJB deployed on weblogic 9.2. I'm using spring (jdk 1.5) to call this remote EJB and the only way I can succeed is to have full weblogic.jar in my bootstrap classpath. Otherwise I get corba error:
CORBA BAD_PARAM 0 No; nested exception is:
org.omg.CORBA.BAD_PARAM: vmcid: 0x0 minor code: 0 completed: No
Interestingly, within same client I have JMS call to weblogic JMS and that fails if weblogic.jar is in boot classpath. Getting rid of weblogic.jar from boot classpath works if I have wlclient.jar and wljmsclient.jar in regular classpath (as per weblogic docs). I would think that for stand alone client all I would need is to weblogic client jars, why should I need to have full weblogic.jar?
I can't get those work together with same classpath. I wonder if anybody has some pointers and/or advice. I was looking to set system parameters for corba for weblogic client that maybe could help:
org.omg.CORBA.ORBClass
org.omg.CORBA.ORBSingletonClass
javax.rmi.CORBA.UtilClass
javax.rmi.CORBA.StubClass
javax.rmi.CORBA.PortableRemoteObjectClass
But I can't find definitive answer.
Regards,
-pp
Edited by mr.papini at 06/28/2007 9:05 AM

I'm stuck exactly with the same issue while trying to port my application from weblogic to jboss.
I tried to specify different ORB implementations (JacORB, OpenORB) for jvm option org.omg.CORBA.ORBClass, but JBoss couldn't get them instantiated. Native Sun implementation which is used in JBoss by default and can be instantiated, apparently is not fully compatible with weblogic security module.
So did you manage to find out the solution?
Edited by DigitalDude at 04/09/2008 11:47 PM

Problems running DII client for consuming webservices

Hello webservices experts,
am running into problems - when I try running my DII client for a webservice that I've successfully deployed on j2sdkee1.4.
The exception goes like this
java.rmi.RemoteException: JAXRPC.JAXRPCSERVLET.28: Missing port information
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:462)
I've searched this forum and others as well. Although a lot of people seem to be having this problem nobody seems to have got it solved. Any way out? The client is a mere copy paste of the DII client example in j2eetutorial 1.4

Solved it ! Some endpoint alias problem during deployment ! Now works fine !

Error: Transaction IDX1: Port SAPRP1, client ,RFC destination contain error

Hi All,
I am faceing the problem while executing the XI ,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
============
It is showing this error and the idoc is not posting to the SAP. When i checked out the IDX2 i am not getting any such structure of our IDOC type, So do i need to create the structure manually, or will it create automaticallywhen the idocs willposted .
Is there any import and export option for this.
Please treat this as urgent , thanks in advance...

Hi Jay,
how did you create port using IDX1 ,I think you must have to follow the naming convention there.Any user given name might not work.
I think in your case , create port as SAPRP1 using IDX1.
can you you give a try with that.port name exactly same as SAPRP1.
you may also refer this link
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Port Knocking client for Symbian?

Similar Messages

Maybe you are looking for