Managed File Transfer

 View Only

Question and Answer from "Diving Deep on the new Connect:Direct 6.0."

  • 1.  Question and Answer from "Diving Deep on the new Connect:Direct 6.0."

    Posted Mon February 04, 2019 01:07 PM
    Edited by System Wed March 22, 2023 11:52 AM
    Thank you for attending our webcast "Diving Deep into the new Connect:Direct 6.0"   We received more questions than we could answer, so we are posting the answers in this forum.   If you have additional questions, please post them below and I will answer them.

    1. Does this version of Connect:Direct (C:D) support containers, like Dockers?

    Answer: C:D doesn't currently support containers, including docker containers.  We are actively working on containerization efforts and would look to support it in the future.  Watch the user community for further developments.  
     
    2. Are there plans to support Kubernetes and Docker Swarm?
     
    Answer: C:D doesn't currently support docker.  We are actively working on containerization efforts however and Kubernetes is a key aspect of that work.  Swarm support is something that we would likely explore in the future.
     
    3. In the future versions, are you going to change the way the events are pushed to IBM control centers?
     
    Answer: We do have an item on the C:D roadmap to transition towards Control Center's Open Server Architecture so that we can move away from the direct polling method we currently use.  Watch the user community for further developments.
     
    4.  Isn’t it a good idea to enable SSP to do the DLP and Virus Scan because it will be done in the DMZ zone itself?
     
    Answer: Yes I agree.  We have seen quite a bit of interest and our development teams have done quite a lot of research in this area.  If this is something you really want, I suggest voting on the outstanding enhancement request at https://watsonsupplychain.ideas.aha.io/ideas/SSP-I-20
     
    5. Many in our organization don't use the UI, so we made enhancements on the C:D Commands and method to generate the reports from Log files for better understanding of the issue.
     
    Answer: We did not make significant changes to the CLI with the v6.0 release. 
     
    6. Is there an option of rebranding the UI page with a company name and logo?
     
    Answer: That is not currently possible.  I would suggest opening an enhancement request so that we can gauge interest. https://watsonsupplychain.ideas.aha.io/?project=CONDIRECT
     
    7. Does C:D 6.0 have full API capability to manage C:D?

    Answer: We can perform most management activities.  Please visit this link which details the available REST APIs.  Support can offer additional guidance if needed.  https://www.ibm.com/support/knowledgecenter/SS4PJT_6.0.0/cd_webservices/cd_webservices_restfulapi/restful_api_overview.html#concept_nrj_l4y_5t
     
    8. How does the 'cloud' transfer performance compare with 'normal' point to point transfers?
     
    Answer: Transfer speeds are not impacted directly by hosting location.  Throughput is typically impacted by network conditions such as bandwidth, latency, and packet loss.  The hosting infrastructure generally doesn't have an impact.  We do support the High-Speed Add-On between on-prem and the cloud if large datasets need to be moved into and out of the cloud.
     
    9. What are your plans for supporting Azure ?
     
    Answer: Unfortunately I cannot discuss targets in a public forum.  Please feel free to have your sales rep contact me and we can setup a roadmap call however where I can detail what our development plans are and general targets for deliveries.
     
    10. In C:D version 6.0 is it possible to have centralized netmap that we can share with all the connect direct nodes?
     
    Answer: You could create a default netmap that could be used across any instances of C:D on a specific OS type (Windows, UNIX, z/OS, etc.).  This netmap would likely give you a very good starting point, but you would likely need to customize it slightly to customize settings for the local nodes entry in the netmap.
     
    11. Would C:D 6.0 allow integration with PEM?
     
    Answer: C:D 6.0 has added REST APIs which are a key building block moving towards PEM (Partner Engagement Manager) support.  PEM would need to leverage these APIs in the future to directly integrate with C:D.
     
    12. What does the Build Transfer/Submit Transfer menu item do?
     
    Answer: It is used to submit one-time transmissions and submit previously written processes.  These capabilities are similar to what is available in Requester and Browser.
     
    13. Is the FileAgent packaged with C:D 6.0 version similar to previous versions? Is there a new version of FileAgent?
     
    Answer: FileAgent (FA) is still distributed with C:D v6.0.  Some enhancements have been made to FA, but the main version number has not changed.
     
    14.  Can you share more about the Rest API capabilities that will be available?
     
    Answer: Please visit the documentation link below that covers REST API capabilities.  If you have further questions support can likely provide some guidance.  https://www.ibm.com/support/knowledgecenter/SS4PJT_6.0.0/cd_webservices/cd_webservices_restfulapi/restful_api_overview.html#concept_nrj_l4y_5t
     
     
    Thank you for the great questions.   If you have additional questions, please post them below and I will be happy to answer them.
     
    Chris Sanders

     

    *copy has been edited for clarity.


    ------------------------------
    Chris Sanders
    ------------------------------
    #filetransfer
    #DataExchange