ecplise without scn

[former_member399810]

Hey,

at the moment I'm playing around with abap in eclipse.

I was able to connect to my desired sap system and to create a new project.

Also I was able to create new classes and interfaces.

But I have problems to create packages, function groups, function modules etc.

I'm getting the error, that eclipse can't connect to my system with an strange ip-adress, when eclipse want to create a gui session.

(why does he want to create a gui session)

The ip-adress, which should be reached, starts with an s (s<xxx>.<xxx>.<xxx>.<xxx>).

In my opinion this comes from the scn.

Unfortunately in the sap scn is not activated.

Is there a way to run abap in eclipse without scn?

[former_member399810]

Hey,

at the moment I'm playing around with abap in eclipse.

I was able to connect to my desired sap system and to create a new project.

Also I was able to create new classes and interfaces.

But I have problems to create packages, function groups, function modules etc.

I'm getting the error, that eclipse can't connect to my system with an strange ip-adress, when eclipse want to create a gui session.

(why does he want to create a gui session)

The ip-adress, which should be reached, starts with an s (s<xxx>.<xxx>.<xxx>.<xxx>).

In my opinion this comes from the scn.

Unfortunately in the sap scn is not activated.

Is there a way to run abap in eclipse without scn?

[schneidermic0]

What are your settings in SAP Logon for your system connection? Is the communication using SNC disabled?

These settings are also taken for the system connection in Eclipse.

Michael

[former_member399810]

no, the scn-option in the sap logon is disabled.

This is because scn is disabled in the sap system.

[gregorw]

Seems the spell checker translates SNC which stands for Secure Network Connection into SCN which is the SAP Community Network :-).

I have no issues using the SAP GUI without SNC. Please try the suggestions of Abdul and me. Also a screen shot of the error message would help.

[gregorw]

I hope you have access to the SAP Service Marketplace. Today at http://service.sap.com/swdc the SP8 of ABAP in Eclipse was released. It should fix the problem when you use IP-Addresses in the SAP Logon.

[former_member399810]

Actually I dont find the Support Package. When I search for the term "Eclipse" I only find version 1.0, but no support package.

[gregorw]

It's a support package for 1.0. Follow the 1.0 link and then # OS independent. There is the SP 8.

[former_member399810]

Thanks, I found it.

Let me check, if someone will install it.

[christoph_ostrop]

Michael Schneider wrote:
What are your settings in SAP Logon for your system connection? Is the communication using SNC disabled? 
These settings are also taken for the system connection in Eclipse.
Michael

is it possible to use ADT (ABAP in Eclipse) without using SNC ???

[schneidermic0]

You should use a secure network connection when you use ABAP development tools.

However, it is technically possible to use ADT without using SNC by using the settings I mentioned above.

[christoph_ostrop]

Michael Schneider wrote:
You should use a secure network connection when you use ABAP development tools.
However, it is technically possible to use ADT without using SNC by using the settings I mentioned above.

do you have a step-by-step documentation or HowTo-Guide to setup SCN ?

i ask some days before, but no answer yet => http://scn.sap.com/thread/3241453

why is everything in SAP all so complicated and very poorly documented

Thanks in advance

[gregorw]

Dear Hendrik,

I also had this issue when using AiE with a SAP Logon entry using an IP Address. It seems that the current release of AiE does always replace the part until the first dot with the hostname of your ABAP backend. So i.e. the IP Address 192.168.0.1 is replaced with host.168.0.1. A simple fix for this problem is to edit the client systems hosts file and add this line:

192.168.0.1     host.168.0.1

It's quite a hack but it works.

Best regards

Gregor

[abdulbasit]

I also had the same problem

I set the FQDN parameter on SAP system and changed the Application Server definition on SAP Logonpad from IP to this FQDN. Then it worked.