FI port types

Hi All
I need to Know the definition and the USAGE (when I use each port) and the protocol used foreach of the FI port types
1- FC uplink port
2- FC storage port
3- FCoE uplink port
4- FCoE storage port
5- Appliance port
thanks in Advance
Amr

Hi Amr
1- FC uplink port
connects FI with native fibrechannel to a North bound FC switch (Brocade, MDS, N5k)
2- FC storage port
connects FI with native fibrechannel to a directly attached storage system
3- FCoE uplink port
connects FI with native FCoE to a North bound FCoE switch (N7k, N5k)
4- FCoE storage port
connects FI with native FCoE l to a directly attached storage system
5- Appliance port
connects FI with a direct attached IP storage system (iSCSI, NFS, CIFS)
There is actually another port type "unified", by first creating a Ethernet uplink, and then on the same port a FCoE uplink. This link will then transport FCoE and data IP traffic.
Walter.

Similar Messages

Creation of client proxy for a WSDL with 2 port types??

Hi,
I am trying to consume an external web service from SAP - ECC6.0. The WSDL file has 2 porttype definitions - one for i/p and one for o/p
When I proceed with SE80 to create a client proxy, it asks me to select any one port type to generate the client proxy. If I select only the input port, it generates proxy for the input port alone.
In this scenario, how do I create proxies and configure logical ports, and call it from a single program to invoke the whole web servie with both i/p and o/p?
TIA,
Regards
Deepthi

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Creating new logical ports for WSDL with several port types not working

Hi all,
I am trying to integrate some BODS webservice into the BPM. I am using CE 7.2 Kernel Version: 7.20.3710. When I am trying to assign a provider system in the application configuration I get following error:
The provider system successfully found the needed service, but its wsdl is without webservice policy. Thus the generated client configuration might not work because of different configurations between service and client (most probable a difference in the security settings). Either assign a provider system with access to wsdl with policy or manually create the client configuration.
The regarding provider system is using a communication profil where the authentication method is set to "none". Normally this configuration should work, but it isn't.
So I started to create new logical ports for each port type. But then I get the error:
Port type name of loaded WSDL does not match the port type name of the Service Reference.
I checked already the port type names in the WSDL but they are 100% the same. What I found was that the configuration is always trying to use the first port type in the WSDL. So I am not able to configure the other port types in the service group.
I also tried to do the same thing using a WSDL with just one port type and surprise it is working...
I hope somebody can help me out
Thanks in advance
Andy

Hi Andy,
Please check this Link: https://cw.sdn.sap.com/cw/docs/DOC-45012
Regards,
Naresh B

Source port type for BPELProcess does not match target port type for EJB

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

In Orchestration View , Port Type is Read only

Hello ,
I am having Request Response Port in Orchestration View (Port Type), i have linked this with Receive Shape and Send Shape in orchestration and deployed this application.
I have realised that my Port Type should be Type Modifier = Public
insted of type Internal.
But it is read only and not allowing me to change it now ????.
One way to do this is create new port type assign it's Type modifier...
Any Ideia how to do that other way ?
Thanks,
Nilesh
Thanks and Regards, Nilesh Thakur.

Thanks Boatseller for help ...
As I already explained that this Port Type was already created (by one of my team member) and deployed.
1) How many way we can create Port Type ?
I know by right click on Port Surface and New Port or New Configure port ???
what I mean is that not able to make changes in property window for
Type Modifier.
This port type is grad out and also All option in property are disabled.
Thanks,
Thanks and Regards, Nilesh Thakur.

What port type should i use?

I am using Seebeyond as middleware and it sending Vehicle IDoc VEHCLE01 to SAP System.
Please help me
what should port type I need to use? Should it be file port or t-rfc port?
What should partner type need to use? Can it be LS type?
Is it ALE or EDI Scenario?
Thanks in advance.

Hi,
Yes, the Port can be a File Port (IDocs will be saved in this folder) or t-rfc port. File port should be OK.
Partner Type can be LS.
Cheers,
Bhanu

Problem with ABAP Port Type

Hello Experts,
My problem is related to Idoc generation using ABAP Port Type.
In the creation of ABAP Port, one Z function module is assigned which has the code to generate another Idoc(MASTER_IDOC_DISTRIBUTE is used inside).
The problem is, I am able to create the first Idoc using this ABAP Port, and in the status, the first Idoc reached 03 with a message that this Idoc number reached the Zfunction module(which is assigned to port). But I'm unable to see the second Idoc generated. Even I am not sure whether this second Idoc generated or not.
Can you please explain how this ABAP Port type behaves, how to get this function module (which is assigned to port) into debugging mode and help me to solve this.
Regards
Sunil

Hello Radha,
Thankyou very much for your reply.
Even though we keep a break point inside the Function Module it will not come into debugging mode. It needs a different procedure.
I will explain again what my requirement is.
We have a port defined as ABAP Port (Not tRFC and not File Port ). While creating this ABAP Port it never asks for RFC destination, but it asks for a Function Module. So we have given that function module also. ( Basically this Function module creates Idocs using MASTER_IDOC_DISTRIBUTE afetr the original Idoc is created and sent to this port. )
So Initially we have generated one Idoc thru shipment which is sent to this ABAP Port. Immediately on reaching this port we got a message that this first Idoc reached this ABAP port and reached the Function Module. But we dont see any new Idocs created using this function module.
We used this Function module in a zprogram and created Idocs which means that the code in FM is working perfectly.
Now the problem is we are not sure whether the firstly created IDoc (on reaching the port) is triggering this Function module or not. We have checked WE02 if any new Idocs created after the initially created Idoc. But we found nothing. The one we created is the latest.
So can anybody explain how this function module (mandatory to give while creating ABAP port) gets triggered? And how can we get this FM in to debugging mode. Is there any link missing out there while defining ABAP port? Please explain.
Thanks you
Best Regards
Sunil

Problem using logical port type "ABAP"

Hi, my problem is that I have to save a txt file with a certanly format who feeds from an IDOCs that is sended nowhere.
Instead of using a BADI the client wants that every time a PO is liberated an IDOC has to be triggered and it has to save that txt in a path, but that IDOC is not sended anywhere is just for saving the file. Dont ask why... they want to do this approach.
So I created a logical port of type ABAP, copy the function "OWN_FUNCTION" as a template and in my custom function I parse the IDOC and save the file... it works. My problem is that the IDOC is created when a PO is created but not triggered !!!
The IDOC is created with status 30 (ready to send).
What I need is that when the PO is saved the file has to be generated in the server but the function is not triggered. I try running the Program RSEOUT00 and the IDOC is not found (dont know why) the only way I can trigger the IDOC is via BD87.
Someone could help me, I dont know why the logical port type ABAP is not triggered. all my setting in WE20 is right.
Thx

The problem was in the WE20, the radio button was in mode 4 (collect IDOCs) instead of 2 (send inmediatly)

Process and initiate operations in port types

What is the difference between the process and initiate operation in the port types definition found in wsdl file? Is this used too define sync and async processes?

Hi.
As far as I understand, process and initiate are just naming conventions. What really makes the difference is that, for sync processes you have a single portType with an input/output operation, and for async processes you have two portType definitions, each one containing an input only operation.
For sync processes, the requestor makes the call and waits for the response, using the same channel (same port).
For async processes, the requestor makes the call in one port and forget about it. Later on, a callback can be generated through the other port type as a means of notifying the requestor back in an async way.
Regards.
Denis

AIA FP 11.1.1.3. ProvABCSImpl Port type issue.

Hi,
Current Config- AIA 11.1.1.3 FP, Weblogic 10.3, Soa Suit - 11.1.1.3, Jdeveloper- 11.1.1.3
Designed ProvABCSImpl Fire and Forget composit using service constructor
and getting given issue.
Error(99,25): Source callback port type for "CreatePurchaseOrderListEbizProvABCSImpl" does not match target callback port type for "CreatePurchaseOrderListEbizProvABCSImplProcess".
Same ProvABCSImpl is getting deployed using AIA 11.1.1.2, Jdev 11.1.1.2, soasuit 11.1.1.2
We feel that issue is with AIA FP 11.1.1.3.
Regards
Manish

Hi Manish,
Can you confirm that the 'CreatePurchaseOrderListEbizProvABCSImpl' is the same port as mentioned in CreatePurchaseOrderListEbizProvABCSImpl.wsdl for handling callback.If that is not the case then remove 'callback' section from [Component_Name].componenttype file for the 'service' tag and try to compile again.
Yeah I feel this is a issue with SOA Suite PS2 version. You should define a separate port for callback operations.
Rgds,
Mandrita.

Stop sign on port type definition in orchestration view

I'm trying to debug an issue with a custom error class thrown from a wcf service.
In my orchestration the port type has what looks like an error indicator:
What does the small stop sign mean? Is this an error indicator from visual studio or an indication that this is a fault message type?
Thanks

boatseller and
Abhishek0127 : Give us a chance to Propose any of your replies as correct :)
@jsprenkle: I would go with boatseller, its just the icon for a Fault message.
Check this article for Fault Message and how it appears in Orchestration
How to handle Fault Message in BizTalk server
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Failed to lookup port type on Mediator Callback

Hi everyone,
I'm new to SOA Suite and to learn it i've started following the book "Getting Started with Oracle Soa Suite: A Hands On Tutorial". In chapter 7 about BPEL i'm getting the following error message when i try to set a callback on the mediator to a BPEL process:
Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
SEVERE: Failed to lookup PortType for {http://xmlns.oracle.com/pcbpel/adapter/file/POProcessing/POProcessing/WriteApprovalResults}Write_ptt in POProcessing/WriteApprovalResults
Nov 6, 2012 9:09:46 PM oracle.tip.tools.ide.fabric.model.WSDLInterface loadOperations
SEVERE: Failed to lookup PortType for {http://oracle.com/sca/soapservice/CreditCardValidation/validationForCC/getStatusByCC}execute_ptt in POProcessing/getCreditCardStatus
I've already acessed the WSDL on browser, tested them on EM and everything seems ok with these two services.
Please, could you help me to solve this error? If you need some code or configuration i can post here.
Best regards,
Hugo

SEVERE: Failed to lookup PortType for...
1. Maybe its just really a different port type and you have it mistyped or something in the calling webservices inside your code (where it makes a call to the WSDL endpoint)
2. It could be that the WSDL basically needs to be local. That is, although its an off the shelf application and all.. you need to download the WSDL on your local computer in a C:\drive or
a location and then use that WSDL file to generate web services from the tool you are using (like eclipse/jdev so on so forth)
what is the port type that you have and the port number ?
-Rtiee

Same Port Type in multiple orchestration

Hi,
I have four ports in "Orchestration A" and four port types for it. I have chosen the same port type (CodecoRcvPortType) for another port in "Orchestration B" in the same project. But i am not able choose the operation for the receive
shape. When i checked the port types are as above. Kindly advice.
Regards, Vivin.

If the port type of which you have defined in “Orchestration A” is of type internal (as you’re trying to reuse the port type in
different orchestrations within the project )
or public (which has no restriction), then you can reuse this port type in “Orchestration B” of the same project.
Any one of following reasons could be the cause why you were not able to connect the port to receive shape:
Port type defined in “Orchestration A” is private. So you’re not able to access it in “Orchestration B” of the project
You have not set the “message” property of the Receive shape in “Orchestration B”.
The message type defined to the message set to the Receive shape is different to the message type of the operation to the port type. This can be seen if you check the PortTypeàYourOperationNameàMessage
Type property of the port type.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Nas-port and nas-port-type

I recently replaced my home 1721 running 12.4(3g) with a demo UC520 running 12.4(11r)XW from work to become more familiar with it. I had my 1721 setup for PPTP dial-in with RADIUS authentication back to an SBS 2008 and everything worked great. When I swapped out for the UC520 with the same AAA settings it would not connect. Further inspection found that the nas-port-type and nas-port aaa attributes were not being passed to the RADIUS server so the VPN Access Policy was not being used. Is this a bug or do I need to tweak a few things for this version of IOS?
Any tips would be appreciated.
I recently replaced my home 1721 running 12.4(3g) with a demo UC520 running 12.4(11r)XW from work to get more familiar with it. I had my 1721 setup for PPTP dial-in with RADIUS authentication back to an SBS 2008 and everything worked great. When I swapped out for the 520 with the same AAA settings it would not connect. Further inspection found that the nas-port-type and nas-port aaa attributes were not being passed to the RADIUS server so the VPN Access Policy was not being used. Is this a bug or do I need to tweak a few things for this version of IOS?
Any tips would be appreciated.

Make sure that you have configured the ISAKMP policy in UC520.

STP Port type Network in VPC

Hi All,
I have a topology like two vpc peer connected to down catalyst switch 3750 with VPC 51. My left switch is primary in VPC and other is secondary.
if i enable spanning tree port type Network on VPC member ports and peer link. Then Secondary peer device start generating BPDU's and advertise its own bridge ID to Down host swich.
Then Can you explain how down switch react to that because in this scenario down switch recieve two different Bridge ID's one from Primary and other from Secondary on same port channel which is logical one port.
How it gonna handle this?
I read regardless of the Spanning-tree root, VPC primay always generate BPDU and seconday device only rely that bpdu and never generate itself.
what if somebody enable spanning tree port type Network towards down host switch on VPC member ports. Type network would generate BPDU's.

Hie Bhanu,
The STP is working as expected in your design. For a gig port port cost is 4. So for 1st 2950 cost to root is 8 thr 3550a. For 2nd 2950 cost to root is 12 thr 3550a and 16 thr 3550b so first one in preferred and later one is blocked. But for 3rd 2950 cost to root is 16 thr 3550a but thr 3550 b it is 12. Hence 3rd 2950 forwards traffic thr 3550b-6513b-6513a. This operation seems to be ok unless you have some specific requirements to change.
Changing port channel cost is not a good idea. both the 6500s are using this channel for communication between them. If you block this link, the 6500s will have to communicate thr all the access switches which is not a good design.

FI port types

Similar Messages

Maybe you are looking for