Solved: JDI Configuration

Hi,

We are currently on EP6 SP14 and are configure JDI.

Following the JDI Configuration guide I have done the deployment of JDI content and configured the security (i.e. create users, assign roles and Groups), activated the SLD on the same server and supplied the data to the SLD from visual admin tool.

But when I select the system and see the URl it shows <Host name>:50000 instead of <Fully qualified domain name>:50000 in the below path.

(http://<Fully Qualified domain name>:50000/SLD -

> System Landscape--

> Technical Landscape---> Web As Java)

The host name of the system is fully qualified domain name, but the inputs given at the time of the EP6 installation was not fully qualified domain name, does this impact?

I also see the Message Server, Enqueue Server host name is not fully qualified domain name.

Can any one help me in resolving the problem?

Thanks,

Sandeep Doma

SAP Managed Tags:
NW Java Development Infrastructure (NWDI)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Sandeep,

As far as i know if all the systems are in the same domain then this shouldnt be a big problem for you. Even if there is a problem you can get in touch with the Network Administrator and they can help you fix this.

However one more thing can be done. You have said that in the WebAS Java system in SLD you dont get to see the fully qualified domain name.

For this you can log in to Visual Administrator go to SLD Data Supplier service. There under the CIM Client generation tab make sure that when you have given the host name you have specified the fully qualified domain name. If not specify that. Then go to tab HTTP settings again specify the fully qualified domain name and there press the button "Trigger Data Transfer to SLD". Then you can go and check the SLD again.

But really this will not matter if all the systems are in the same domain and you plan to access from within the domain.

This link will be able to help you.

http://help.sap.com/saphelp_nw04s/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm

Regards

Sidharth

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sidharth,

Hostname in the SLD data supplier is fully qualified domain name(i.e. Http and Cim).

when i go to http://<hostname>:50000/devinf--->Change Management Service -

> and click the SLD in the top level navigation it goes to http://<hostname>:50000/sld which does not open a page,as it is not fully qualified domain name.

I think the host name should be fully qualified domain name but i am not able to know where to change it.

Thanks,

Sandeep

Ok this name has to be changed in the Landscape Configurator.

When you login to CMS just click on Landscape Configurator. There under the tab page Domain Data you will find that you have to specify the SLD URL. Here you will have to specify fully qualified domain name.

Save the domain and update the CMS.

Hope this is what you are looking for.

Regards

Sidharth

Hi Sidharth,

I have congigured JDI and am able to connect to the DTR but getting the below error, any idea?

com.sap.tc.devconf.SyncException: Import configuration failed:Could not create mountpoint for SC in compartment sap.com_SAP-JEE_1: Checking existence failed for /dtr/ws/test1234/sap.com_SAP-JEE/dev/inactive/SCs/sap.com/SAP-JEE/_comp/TopLevelDCs/(Internal Server Error)

at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:811)

at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:633)

at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:604)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.addDevConf(DevConfWizard.java:279)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.access$000(DevConfWizard.java:46)

at com.sap.ide.eclipse.component.wizard.DevConfWizard$1.run(DevConfWizard.java:156)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:154)

at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)

at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)

at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)

at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)

at org.eclipse.jface.window.Window.open(Window.java:563)

at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)

at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)

at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)

at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1391)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)

at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)

at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)

at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)

at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)

at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)

at com.sap.ide.eclipse.startup.Main.run(Main.java:789)

at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

Caused by: com.sap.tc.devconf.RepositoryAccessException: Could not create mountpoint for SC in compartment sap.com_SAP-JEE_1: Checking existence failed for /dtr/ws/test1234/sap.com_SAP-JEE/dev/inactive/SCs/sap.com/SAP-JEE/_comp/TopLevelDCs/(Internal Server Error)

at com.sap.tc.devconf.impl.DevelopmentConfiguration.<init>(DevelopmentConfiguration.java:343)

at com.sap.tc.devconf.DevelopmentConfigurationFactory.addConfiguration(DevelopmentConfigurationFactory.java:779)

... 44 more

Caused by: com.sap.tc.devconf.SyncException: Could not create mountpoint for SC in compartment sap.com_SAP-JEE_1: Checking existence failed for /dtr/ws/test1234/sap.com_SAP-JEE/dev/inactive/SCs/sap.com/SAP-JEE/_comp/TopLevelDCs/(Internal Server Error)

at com.sap.tc.devconf.impl.DTRClientErrorMapper.toSyncException(DTRClientErrorMapper.java:73)

at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2821)

at com.sap.tc.devconf.impl.DevelopmentConfiguration.createMountPointsForSCs(DevelopmentConfiguration.java:3070)

at com.sap.tc.devconf.impl.DevelopmentConfiguration.<init>(DevelopmentConfiguration.java:341)

... 45 more

Caused by: com.tssap.dtr.client.lib.vfs.config.ConfigurationException: Checking existence failed for /dtr/ws/test1234/sap.com_SAP-JEE/dev/inactive/SCs/sap.com/SAP-JEE/_comp/TopLevelDCs/(Internal Server Error)

at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.getRemoteCollection(RepositoryServer.java:419)

at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.getLowestExistingCollection(RepositoryServer.java:398)

at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.assureRemotePathExists(RepositoryServer.java:184)

at com.sap.tc.devconf.impl.DevelopmentConfiguration.findOrCreateMountPointForSC(DevelopmentConfiguration.java:2811)

... 47 more

Caused by: com.tssap.dtr.client.lib.deltavlib.DeltavException: Internal Server Error

at com.tssap.dtr.client.lib.deltavlib.impl.DeltavCommand.checkResponseStatus(DeltavCommand.java:104)

at com.tssap.dtr.client.lib.deltavlib.impl.DeltavCommand.execute(DeltavCommand.java:51)

at com.tssap.dtr.client.lib.deltavlib.impl.AbstractResource$PropFinder.load(AbstractResource.java:992)

at com.tssap.dtr.client.lib.deltavlib.impl.cache.HashmapPropCache.refresh(HashmapPropCache.java:244)

at com.tssap.dtr.client.lib.deltavlib.impl.AbstractResource.refresh(AbstractResource.java:587)

at com.tssap.dtr.client.lib.deltavlib.impl.ResourceLocatorFactoryImpl.createCollection(ResourceLocatorFactoryImpl.java:215)

at com.tssap.dtr.client.lib.vfs.config.impl.RepositoryServer.getRemoteCollection(RepositoryServer.java:416)

... 50 more

Caused by:

com.sap.tc.devconf.RepositoryAccessException: Could not create mountpoint for SC in compartment sap.com_SAP-JEE_1: Checking existence failed for /dtr/ws/test1234/sap.com_SAP-JEE/dev/inactive/SCs/sap.com/SAP-JEE/_comp/TopLevelDCs/(Internal Server Error)