unable to access register button in service maintenance

[former_member182645]

Hi All

1) Unable to access button register in service maintenance.

able to register service in /iwfnd/maint_service.

2) after generation of service , service took LOCAL as system alise.

[Former Member]

Hi,

i think the SEGW has some bugs. I've got a fully working environment with backend (erp system) connected to gateway-hub (gw system). everything works fine.

then i copied a service-project to clean it up from runtime artifacts (interfaces not used anymore) and from this point the copied project is no longer able to maintenance, register, errorlog on the hub system... this seems to be a BUG.

on other projects (new created with segw) everything works as expected.

Danilo.

[kammaje_cis]

Radhesh,

Why don't you go to /IWFND/MAINT_SERVICE in your HUB system and 'Register' your service. That is the other way of doing the same thing.

[former_member6142]

Yes, there you can do the following steps:

1. Click Add Service.

2. Fill in your System Alias, usually, you can put LOCAL

It happend to me working with a $tmp package.

[EkanshCapgemini]

Hi Radhesh,

1) In order to make register button enable in SEGW, the project should be in change mode.

2) The system alias is configured in SPRO. You need to configure system alias so that it also gets displayed here in SEGW. Have a look at

Regards,

Ekansh

[former_member182645]

thanks ekansh for quick reply....

i added system in SAP Netweaver gateway setting.

Now system visible in service maintanance.

When try to register server it ask about system alise.

Seams that drop down dont have value so service not registered.

So please let me know where to add system alise so it is visible in drop down box

[former_member182645]

hi ekansh

i added system in SAP Netweaver gateway setting.

but what is destination system? clint and alises i have to give?

coz i am using hub of iw_fnd and gw_core....

if i give hub then able to register service but at testing time its not woking...

show 403 error or serive not available.

[EkanshCapgemini]

There are 2 type of system alias maintained:

1) for registering your gateway service (from the backend system To the Hub system)

2) for the system where your DPC, MPC classes are created (from the Hub system to the Backend system)

I think till now what you have maintained is the first one and thats why now you are able to see the alias in the service maintenance node. Now once you click on register, it asks for the second system alias mentioned above. So you have to add the second alias in SPRO.

Regards,

Ekansh

[Andre_Fischer]

Hi Radesh,

the reason why you don't see any system alias entries offered in the drop down box is probably because you have not maintained the sid and client of the backend system the system alias points to.

This information is needed by the Service Builder to find the system aliases that point from the hub to the backend system. The Service Builder performs a RFC call from the backend to the hub and it retrieves those system aliases that point back to the backend where the Service Builder is started.

This information is not needed when registering the service from withing transactin /IWFND/MAINT_SERVICE as Krishna suggested.

Best Regards,

Andre