on 03-07-2014 11:11 AM
There are several possibilities. Things to check:
1) the optimizer application is deployed properly and is started.
2) the system properties in sourcing application specifically the one containing the URL are set to the correct hostname and port.
3) if the optimizewr is not on the same server as sourcing there are no network restrictions between the two servers.
Regards,
Gary
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gary,
1) the optimizer application is deployed properly and is started.
A: We think Yes, is deployed properly and is started. What means for you "deployed properly"
2) the system properties in sourcing application specifically the one containing the URL are set to the correct hostname and port.
A: What are the correct properties in sourcing application for specifically optimizer server?
3) if the optimizewr is not on the same server as sourcing there are no network restrictions between the two servers.
A: The optimizer is not on the same server as sourcing and no restrictions exist between the two servers.
Thank you for your help,
Regards,
Ana
Hello Jesse,
He did 2 things:
1) We had to delete de "http://" from the url´s on the system properies of the optimization;
2) We installed the optimizer on the same server of the sourcing ( before was in a different server )
Let me know if it worked
Regards
Ana
well, i've got a ticket open with SAP Sourcing support. I didn't have "http:://" prefix set... but optimizer is on a different Netweaver server. I'm not going to install it on the sourcing server. They need to help us figure this out, so i'm gonna leave it as is. Hopefully we'll get it figureed out, and if so... i'll post the solution back here. Thanks a bunch Ana. - jesse
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.