Topic
  • 10 replies
  • Latest Post - ‏2014-08-29T05:34:26Z by WCR6_li_li
WCR6_li_li
WCR6_li_li
15 Posts

Pinned topic Process Server Config

‏2013-07-05T03:23:26Z |

I installed my process server by default.  I access the server by Process Designer,  when the client and the server locate in the same subnetwork, it is OK. Otherwise ,I can't get the connection .

For example , the process server IP is 192.168.63.10, developer A's  IP is 192.168.63.50, developer A can access the server by process designer; developer B's  IP is 192.168.64.50, developer B can't access the server by process designer.

 

What config need to do for solving the problem?

  • vlit
    vlit
    931 Posts

    Re: Process Server Config

    ‏2013-07-05T05:58:58Z  

    Hi,

    It is not a problem of BPM environment but of your network settings.

    Ask your sysadmin. He knows what to do.

    If you have not one, send me the result of the command on your server.

    route (Linux)

    or

    route print (Win).

    and

    tracert 192.168.63.10

    from clients.

     

    Vlad.

    Updated on 2013-07-05T06:00:25Z at 2013-07-05T06:00:25Z by vlit
  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2013-07-05T06:26:56Z  

    My PC IP is  192.168.149.104 and sys is Windows, the process server IP is : 192.168.66.50

     

    The result of route print :

     

    ===========================================================================
    接口列表
     18...00 26 2d fe 31 e9 ......Intel(R) 82577LM Gigabit Network Connection
     14...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
      1...........................Software Loopback Interface 1
     24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
     25...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
     21...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
    ===========================================================================

    IPv4 路由表
    ===========================================================================
    活动路由:
    网络目标        网络掩码          网关       接口   跃点数
              0.0.0.0          0.0.0.0    192.168.149.1  192.168.149.104     10
            127.0.0.0        255.0.0.0            在链路上         127.0.0.1    306
            127.0.0.1  255.255.255.255            在链路上         127.0.0.1    306
      127.255.255.255  255.255.255.255            在链路上         127.0.0.1    306
         192.168.88.0    255.255.255.0            在链路上      192.168.88.1    276
         192.168.88.1  255.255.255.255            在链路上      192.168.88.1    276
       192.168.88.255  255.255.255.255            在链路上      192.168.88.1    276
        192.168.149.0    255.255.255.0            在链路上   192.168.149.104    266
      192.168.149.104  255.255.255.255            在链路上   192.168.149.104    266
      192.168.149.255  255.255.255.255            在链路上   192.168.149.104    266
            224.0.0.0        240.0.0.0            在链路上         127.0.0.1    306
            224.0.0.0        240.0.0.0            在链路上   192.168.149.104    266
            224.0.0.0        240.0.0.0            在链路上      192.168.88.1    276
      255.255.255.255  255.255.255.255            在链路上         127.0.0.1    306
      255.255.255.255  255.255.255.255            在链路上   192.168.149.104    266
      255.255.255.255  255.255.255.255            在链路上      192.168.88.1    276
    ===========================================================================
    永久路由:
      网络地址          网络掩码  网关地址  跃点数
         192.168.11.0    255.255.255.0    192.168.60.55       1
    ===========================================================================

    IPv6 路由表
    ===========================================================================
    活动路由:
     如果跃点数网络目标      网关
      1    306 ::1/128                  在链路上
     14    276 fe80::/64                在链路上
     14    276 fe80::a8fd:6ffb:bdb8:6ccf/128
                                        在链路上
      1    306 ff00::/8                 在链路上
     14    276 ff00::/8                 在链路上
    ===========================================================================
    永久路由:
      无

     

     

    The result of tracert:

    tracert 192.168.66.50

    通过最多 30 个跃点跟踪
    到 BPM [192.168.66.50] 的路由:

      1    <1 毫秒   <1 毫秒   <1 毫秒 192.168.149.1
      2     1 ms     1 ms     1 ms  192.168.0.1
      3    <1 毫秒   <1 毫秒   <1 毫秒 192.168.60.24
      4    <1 毫秒   <1 毫秒   <1 毫秒 BPM [192.168.66.50]

    跟踪完成。

     

     

  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2013-07-05T06:37:41Z  

    My PC IP is  192.168.149.104 and sys is Windows, the process server IP is : 192.168.66.50

     

    The result of route print :

     

    ===========================================================================
    接口列表
     18...00 26 2d fe 31 e9 ......Intel(R) 82577LM Gigabit Network Connection
     14...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
      1...........................Software Loopback Interface 1
     24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
     25...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
     21...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
    ===========================================================================

    IPv4 路由表
    ===========================================================================
    活动路由:
    网络目标        网络掩码          网关       接口   跃点数
              0.0.0.0          0.0.0.0    192.168.149.1  192.168.149.104     10
            127.0.0.0        255.0.0.0            在链路上         127.0.0.1    306
            127.0.0.1  255.255.255.255            在链路上         127.0.0.1    306
      127.255.255.255  255.255.255.255            在链路上         127.0.0.1    306
         192.168.88.0    255.255.255.0            在链路上      192.168.88.1    276
         192.168.88.1  255.255.255.255            在链路上      192.168.88.1    276
       192.168.88.255  255.255.255.255            在链路上      192.168.88.1    276
        192.168.149.0    255.255.255.0            在链路上   192.168.149.104    266
      192.168.149.104  255.255.255.255            在链路上   192.168.149.104    266
      192.168.149.255  255.255.255.255            在链路上   192.168.149.104    266
            224.0.0.0        240.0.0.0            在链路上         127.0.0.1    306
            224.0.0.0        240.0.0.0            在链路上   192.168.149.104    266
            224.0.0.0        240.0.0.0            在链路上      192.168.88.1    276
      255.255.255.255  255.255.255.255            在链路上         127.0.0.1    306
      255.255.255.255  255.255.255.255            在链路上   192.168.149.104    266
      255.255.255.255  255.255.255.255            在链路上      192.168.88.1    276
    ===========================================================================
    永久路由:
      网络地址          网络掩码  网关地址  跃点数
         192.168.11.0    255.255.255.0    192.168.60.55       1
    ===========================================================================

    IPv6 路由表
    ===========================================================================
    活动路由:
     如果跃点数网络目标      网关
      1    306 ::1/128                  在链路上
     14    276 fe80::/64                在链路上
     14    276 fe80::a8fd:6ffb:bdb8:6ccf/128
                                        在链路上
      1    306 ff00::/8                 在链路上
     14    276 ff00::/8                 在链路上
    ===========================================================================
    永久路由:
      无

     

     

    The result of tracert:

    tracert 192.168.66.50

    通过最多 30 个跃点跟踪
    到 BPM [192.168.66.50] 的路由:

      1    <1 毫秒   <1 毫秒   <1 毫秒 192.168.149.1
      2     1 ms     1 ms     1 ms  192.168.0.1
      3    <1 毫秒   <1 毫秒   <1 毫秒 192.168.60.24
      4    <1 毫秒   <1 毫秒   <1 毫秒 BPM [192.168.66.50]

    跟踪完成。

     

     

    I can access the Process Admin console by IE ,so the net connection is OK.

    Such as http://192.168.66.50:9080/ProcessAdmin/login.jsp

  • vlit
    vlit
    931 Posts

    Re: Process Server Config

    ‏2013-07-05T06:48:44Z  

    I can access the Process Admin console by IE ,so the net connection is OK.

    Such as http://192.168.66.50:9080/ProcessAdmin/login.jsp

    > I can access the Process Admin console by IE ,so the net connection is OK.

    It's important remark.

    But may be your firewall blocks another ports?

    BTW what hostname or IP was set in eclipse.ini on your workstation?

     

  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2013-07-05T07:03:37Z  
    • vlit
    • ‏2013-07-05T06:48:44Z

    > I can access the Process Admin console by IE ,so the net connection is OK.

    It's important remark.

    But may be your firewall blocks another ports?

    BTW what hostname or IP was set in eclipse.ini on your workstation?

     

    I have closed the firewall .

    The config in eclipse.ini  is   -Dcom.ibm.bpm.processcenter.url="http://192.168.66.50:9080"

     

    I got the error log from Process Designer log file orbtrc.05072013.1454.16

     

     

     

     

    14:54:16.837 com.ibm.ws.orbimpl.transport.WSTransport getHostIPAddress:137 Thread-10 ORBRas[default]  java.net.UnknownHostException: BPM
     at java.net.InetAddress.getAllByName0(InetAddress.java:1263)
     at java.net.InetAddress.getAllByName(InetAddress.java:1185)
     at java.net.InetAddress.getAllByName(InetAddress.java:1107)
     at java.net.InetAddress.getByName(InetAddress.java:1057)
     at com.ibm.CORBA.transport.TransportBase.getHostIPAddress(TransportBase.java:133)
     at com.ibm.rmi.iiop.TransportManager.getHostIPAddress(TransportManager.java:184)
     at com.ibm.rmi.Profile.getHostIPAddress(Profile.java:476)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getHostfromProfile(SecurityConnectionInterceptor.java:2685)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKeyForLocateRequest(SecurityConnectionInterceptor.java:1419)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKey(SecurityConnectionInterceptor.java:1282)
     at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:293)
     at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
     at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
     at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)
     at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
     at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
     at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
     at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3751)
     at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
     at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1529)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1394)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:949)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:866)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:546)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
     at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
     at javax.naming.InitialContext.lookup(InitialContext.java:455)
     at com.ibm.WebSphereSecurityImpl.SecurityServerImpl.getSecurityServer(SecurityServerImpl.java:255)
     at com.ibm.WebSphereSecurityImpl.SecurityServerImpl.<init>(SecurityServerImpl.java:88)
     at java.lang.J9VMInternals.newInstanceImpl(Native Method)
     at java.lang.Class.newInstance(Class.java:1325)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.getSecurityServer(VaultImpl.java:620)
     at com.ibm.ws.security.auth.ContextManagerImpl.getSecurityServer(ContextManagerImpl.java:2034)
     at com.ibm.ws.security.auth.ContextManagerImpl.access$400(ContextManagerImpl.java:339)
     at com.ibm.ws.security.auth.ContextManagerImpl$10.run(ContextManagerImpl.java:3819)
     at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4566)
     at com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(ContextManagerImpl.java:4634)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3817)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3684)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3680)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3451)
     at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:115)
     at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:111)
     at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
     at com.ibm.ws.naming.util.SecurityUtil.login(SecurityUtil.java:109)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:834)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:546)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
     at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
     at javax.naming.InitialContext.lookup(InitialContext.java:455)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.lookup(ServiceLocator.java:230)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.getSubject(ServiceLocator.java:365)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.getSubject(ServiceLocator.java:351)
     at com.lombardisoftware.client.delegate.common.WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.java:165)
     at com.lombardisoftware.client.delegate.ClientServicesDelegateDefault.loginCheck(ClientServicesDelegateDefault.java:2251)
     at com.lombardisoftware.client.ae.server.ServerPlugin.initialize(ServerPlugin.java:117)
     at com.lombardisoftware.client.ae.server.ServerPlugin.authenticate(ServerPlugin.java:85)
     at teamworks.ae.product.splash.InteractiveSplashHandler$Authenticate.run(InteractiveSplashHandler.java:778)
     at java.lang.Thread.run(Thread.java:736)

  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2013-07-05T07:16:57Z  

    I have closed the firewall .

    The config in eclipse.ini  is   -Dcom.ibm.bpm.processcenter.url="http://192.168.66.50:9080"

     

    I got the error log from Process Designer log file orbtrc.05072013.1454.16

     

     

     

     

    14:54:16.837 com.ibm.ws.orbimpl.transport.WSTransport getHostIPAddress:137 Thread-10 ORBRas[default]  java.net.UnknownHostException: BPM
     at java.net.InetAddress.getAllByName0(InetAddress.java:1263)
     at java.net.InetAddress.getAllByName(InetAddress.java:1185)
     at java.net.InetAddress.getAllByName(InetAddress.java:1107)
     at java.net.InetAddress.getByName(InetAddress.java:1057)
     at com.ibm.CORBA.transport.TransportBase.getHostIPAddress(TransportBase.java:133)
     at com.ibm.rmi.iiop.TransportManager.getHostIPAddress(TransportManager.java:184)
     at com.ibm.rmi.Profile.getHostIPAddress(Profile.java:476)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getHostfromProfile(SecurityConnectionInterceptor.java:2685)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKeyForLocateRequest(SecurityConnectionInterceptor.java:1419)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKey(SecurityConnectionInterceptor.java:1282)
     at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:293)
     at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
     at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
     at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)
     at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
     at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:307)
     at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:378)
     at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3751)
     at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3262)
     at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3649)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1529)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getWsnNameService(WsnInitCtxFactory.java:1394)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:949)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:866)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:546)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
     at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
     at javax.naming.InitialContext.lookup(InitialContext.java:455)
     at com.ibm.WebSphereSecurityImpl.SecurityServerImpl.getSecurityServer(SecurityServerImpl.java:255)
     at com.ibm.WebSphereSecurityImpl.SecurityServerImpl.<init>(SecurityServerImpl.java:88)
     at java.lang.J9VMInternals.newInstanceImpl(Native Method)
     at java.lang.Class.newInstance(Class.java:1325)
     at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.getSecurityServer(VaultImpl.java:620)
     at com.ibm.ws.security.auth.ContextManagerImpl.getSecurityServer(ContextManagerImpl.java:2034)
     at com.ibm.ws.security.auth.ContextManagerImpl.access$400(ContextManagerImpl.java:339)
     at com.ibm.ws.security.auth.ContextManagerImpl$10.run(ContextManagerImpl.java:3819)
     at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4566)
     at com.ibm.ws.security.auth.ContextManagerImpl.runAsSpecified(ContextManagerImpl.java:4634)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3817)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3684)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3680)
     at com.ibm.ws.security.auth.ContextManagerImpl.login(ContextManagerImpl.java:3451)
     at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:115)
     at com.ibm.ws.naming.util.SecurityUtil$1.run(SecurityUtil.java:111)
     at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
     at com.ibm.ws.naming.util.SecurityUtil.login(SecurityUtil.java:109)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:834)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:546)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
     at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
     at javax.naming.InitialContext.lookup(InitialContext.java:455)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.lookup(ServiceLocator.java:230)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.getSubject(ServiceLocator.java:365)
     at com.lombardisoftware.client.delegate.common.ServiceLocator.getSubject(ServiceLocator.java:351)
     at com.lombardisoftware.client.delegate.common.WebsphereDelegateHelper.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.java:165)
     at com.lombardisoftware.client.delegate.ClientServicesDelegateDefault.loginCheck(ClientServicesDelegateDefault.java:2251)
     at com.lombardisoftware.client.ae.server.ServerPlugin.initialize(ServerPlugin.java:117)
     at com.lombardisoftware.client.ae.server.ServerPlugin.authenticate(ServerPlugin.java:85)
     at teamworks.ae.product.splash.InteractiveSplashHandler$Authenticate.run(InteractiveSplashHandler.java:778)
     at java.lang.Thread.run(Thread.java:736)

    Thanks a lot .

    I have resolved it by add one item in hosts

  • nroubal
    nroubal
    4 Posts

    Re: Process Server Config

    ‏2013-07-08T17:28:28Z  

    Thanks a lot .

    I have resolved it by add one item in hosts

    WCR6_li_li

    I am having the same issue and see that you have a resolution by adding an item in the hosts file.

    I was wondering if you could provide this solution in more detail so I can attempt the fix as well?

    Thanks

  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2013-07-09T00:43:04Z  
    • nroubal
    • ‏2013-07-08T17:28:28Z

    WCR6_li_li

    I am having the same issue and see that you have a resolution by adding an item in the hosts file.

    I was wondering if you could provide this solution in more detail so I can attempt the fix as well?

    Thanks

    Process Designer communicate whith Process Server by host name not IP address.

    So when I write "  -Dcom.ibm.bpm.processcenter.url="http://192.168.66.50:9080"  in eclipse.ini.

    First  Process Designer find the computer of Process Server,and it find server's name is "BPM" ,but when Process Designer communicate with Process Server by "BPM", it find cna't resolve the name to IP address.  When I add one item "192.168.66.50 BPM"  in hosts file (lwhich computer Process Designer locate),the problem resolved.

  • AndrewPaier
    AndrewPaier
    847 Posts

    Re: Process Server Config

    ‏2013-07-09T21:11:48Z  

    Process Designer communicate whith Process Server by host name not IP address.

    So when I write "  -Dcom.ibm.bpm.processcenter.url="http://192.168.66.50:9080"  in eclipse.ini.

    First  Process Designer find the computer of Process Server,and it find server's name is "BPM" ,but when Process Designer communicate with Process Server by "BPM", it find cna't resolve the name to IP address.  When I add one item "192.168.66.50 BPM"  in hosts file (lwhich computer Process Designer locate),the problem resolved.

    In general you really shouldn't be installing your server against the IP address of the server.  A Fully Qualified Domain Name (FQDN) is preferred if it is a true server in an enterprise setting.  Baring that you can use the machine name.  IP Address is likely the worst option there is.  

    But I'm going to bet that this wasn't really installed against the IP Address, that is just how you got to the server.  Looks like you installed against the host name of "BPM".  That name winds up being stored in several of the configuration files (you can see it isn the TeamworksConfiguration.running.xml file) and when the Process Designer connects via http it asks the server "Hey for all of these other protocols I need to use, where should I call you back?"  The Process Center looks in its configuration files and says "Apparently my name is 'BPM' and you should use port XYZ for that protocol".

    The problem you ran into (and solved via your etc/hosts entry I'm guessing) is if you ping 'BPM' from you client machine the name does not resolve so you can't finish connecting.  This is because your domain name controller doesn't seem to have 'BPM' as the server name in its list.  By putting it in the etc/hosts file and giving it an ip address you have effectively told you machine how to resolve that name.

    The problem with your configuration is that everyone who does development will need to make that correction to make this work.  And likely there are some other things that will be wrong, such as the server name for WSDLs etc.  You really should get a real FQDN as the name used on the installation of your server and make sure it resolves for everyone on the network.

    Andrew Paier  |  Director  |  BP3 Global, Inc.
    BP3 Global's Website  |  Twitter  |  Linkedin  |  Google+  |  Blogs

  • WCR6_li_li
    WCR6_li_li
    15 Posts

    Re: Process Server Config

    ‏2014-08-29T05:34:26Z  

    In general you really shouldn't be installing your server against the IP address of the server.  A Fully Qualified Domain Name (FQDN) is preferred if it is a true server in an enterprise setting.  Baring that you can use the machine name.  IP Address is likely the worst option there is.  

    But I'm going to bet that this wasn't really installed against the IP Address, that is just how you got to the server.  Looks like you installed against the host name of "BPM".  That name winds up being stored in several of the configuration files (you can see it isn the TeamworksConfiguration.running.xml file) and when the Process Designer connects via http it asks the server "Hey for all of these other protocols I need to use, where should I call you back?"  The Process Center looks in its configuration files and says "Apparently my name is 'BPM' and you should use port XYZ for that protocol".

    The problem you ran into (and solved via your etc/hosts entry I'm guessing) is if you ping 'BPM' from you client machine the name does not resolve so you can't finish connecting.  This is because your domain name controller doesn't seem to have 'BPM' as the server name in its list.  By putting it in the etc/hosts file and giving it an ip address you have effectively told you machine how to resolve that name.

    The problem with your configuration is that everyone who does development will need to make that correction to make this work.  And likely there are some other things that will be wrong, such as the server name for WSDLs etc.  You really should get a real FQDN as the name used on the installation of your server and make sure it resolves for everyone on the network.

    Andrew Paier  |  Director  |  BP3 Global, Inc.
    BP3 Global's Website  |  Twitter  |  Linkedin  |  Google+  |  Blogs

    Thanks a lot.

    I can't deal it like what you have said.

    In my company , server and client locate in different subnet . No domain server .