Welcome To Support Community

Pipeline Pilot

Advanced Search
Ask Search:
TonTon (Accelrys, Inc.)  

I posted an example protocol to the Protocol Exchange for a Generate Frequencies component for two properties (not enough time to generalize this for n properties!). For the automobile data set it will give you the following results:


Best Answer chosen by Ton (Accelrys, Inc.) 
IanIan (BIOVIA) 
Very nice protocol! I modified your example so it should now work for N properties entered as an array of properties on the component.
How can I create a shorter protocol link ?
instead of http://server:9944/webport/default/main.htm?protocol=Protocols/Web%20Services/SomeFolder/MyProtocol
I would like to have a shortcut, something like http://server/myprotocol

Thanks !!

Best Answer chosen by Cypryan (Symyx Technologies, Inc.) 
Michael Peeler (BIOVIA)Michael Peeler (BIOVIA)
If you just want a link to run the protocol, you can use:




or, if you like cryptic,


using the GUID of the protocol. You can find a protocol's GUID by opening the protocol in the PLP client and looking in the Information tab (switch on from the View > Component Windows menu if necessary). Click on the line "Component Type GUID" and select+copy the GUID value from the Help panel.

Another way to approach this is to create a routing layer in a package configuration, where you can map any URL to your protocol, or maybe a whole family of REST URLs to multiple protocols. This is described in the RESTful Web Services Guide in the Developer section of the Help Center. Actually, that also covers the information above. It also covers the various URL query string parameters you can use to determine how the results of the protocol are to be passed back to the caller.

HOWEVER, your URL was explicitly running the protocol inside Web Port, and if you want to stick with that approach, then I think you have to invoke Web Port with your protocol referenced in the query string. I think the shortest you could make it is:


using the GUID, but you may not like to see the GUID in the Web Port GUI!

You could also defne your own aliases, using a package-based extension to the apache httpd.conf file, but I don't know if you really want to go that far?

Anyway, that's about all I can think of right now!
Dear all,

I am currently packaging a few applications in Pipeline Pilot and wondered if there is a way to add dependencies for installation of a package that also includes version numbers to ensure the correct functioning of the package. 
How can I achieve this, currently I only seem to be able to define dependencies using the vendor/packagname syntax. 

If not yet available it would be a nice add-on for future releases of Pipeline Pilot.


Best Answer chosen by peter.schmidtke
AlyonaAlyona (BIOVIA) 
Dear Peter,

Thank you for the request. The enhancement is scheduled for a future release, PPP-40318.

Kind regards,
I'm trying to perform a POST method to a RESTful API web service that is expecting an accompanying tab-delimited text file upload.
Using curl this would be done using the [-T, --upload-file] option but I'm no sure if the HTTP Connector provides the same functionality.

Any pointers would be much appreciated
Thanks very much
Best Answer chosen by TMagnay
Hi - I've solved this for my immediate use case.

To use the HTTP Connector to transmit a file I used the Binary Reader component to read in teh file , piped that into the HTTP Connector and made the binary data the content of the Request Body.

HTTP Connector Parameter Settings:
HTTP Body Content: Send Request Body
Request Body: Binary
Content Type: text/plain --- this would change depending on the content of the file being transfered

To capture the response from the Web Service I used the Data from XML component in hte method largely analogous to what is described in the Biovia Web Services documentation. I did add an 'Additional Allowed Response' in the HTTP Connector so that I could parse "Bad Request" responses without the component generating an error.

I am currently setting up a PP 2017R2 server with LDAP connected authentication by using Kerberos on a RHEL 7 machine. Kerberos has been configured on the system and is working just fine (I can login with my AD accounts on the linux box).
In the Authentication/Security Settings of the Pipeline Pilot server I clicked Allow SPNEGO (Kerberos) and didn’t change any other settings.
I can now login to the Server with my pipeline Pilot Client with my AD credentials.
However, when I want to access the admin page for example (or whatever other web resource) I get a popup window asking me to authentify (screenshot attached)

I tried every possible login/pw local and AD account and nothing works. I can only click cancel and the popup disappears and then I can use the classical web login (shown below the popup) where authentication works.
I noticed that this popup only shows up when I activate the Kerberos Authentication in the PP admin page.
How can I get rid of this authentication Popup ?
Thanks in advance

Best Answer chosen by peter.schmidtke
Stephen PickettStephen Pickett
Hi Peter
We had the same issue when this setting was on with previous versions of PP. We use PAM to access our LDAP rather than touching the default machine authentication. In this case you can turn off Kerberos and the pop up disappears.

Is there any way on a per protocol basis to not show the webport progress bar?  For short running protocols of 1-3 seconds I'd prefer it simply not to show.

Alternatively, is there a way I can the style of it be changed, perhaps to something like a rotating circle (like the admin portal uses).  Again ideally I'd like to control this behaviour on a per protocol basis.

I can't see anything in the customise webport guides for doing this, but I seems to remember someone once telling me it was possible. 


Best Answer chosen by Joe_B
LynnLynn (Accelrys) 
Hello Joe,

There is no supported way to do this.  If you create a support ticket we would be happy to enter an enhancement request on your behalf.

Best wishes,
Lynn Miller
BIOVIA Services
Dear all,

how can I get rid of the label automatically added to some ligand depictions stating AND Enantiomer. I tried to fiddle around with the depiction options, molecular information & properties, but cannot find how to do that.

Thanks in advance.

Best Answer chosen by peter.schmidtke
Hi Peter,

In the HTML Molecular Table Viewer stereochemistry depiction options you can set the chirality label options to custom labels then set the labels to whatever you want - including none but keep the commas. You might also want to turn off the display labels if you've got enhanced stereochemistry.

Looks like you can also create and use an xml file to do this globally rather than for each separate component but I haven't tried this.

Hope I've understood your question, and this helps.

Hello all,

I'd like to know which are the formats supported to input data into a Pipeline Pilot protocol. I already know it can work with excel files and CSV... But I'd be interested to know if it can be coupled with Oracle Databases, etc.

Thank you
Best Answer chosen by jud1
AndreiAndrei (BIOVIA) 
Pipeline Pilot supports reading from and writing to Oracle databases (as well as My SQL, SQL Server and DB2 databases) using a set of components found under Components/Database and Application Integration/Database Access. The most useful is probably the SQL Select component, which allows you to enter a SQL query and will output Pipeline Pilot data records for each result returned by the query. Another useful component is the SQL Select for Each Data component, which allows you to run a query for each incoming data record. I hope this helps.

We recently had an application server updated such that it now runs TLS 1.2 (high security level).
Unfortunately now the copious number of protocols I've written that heavily use the HTTP Connector component to trigger  GET / PUT / PUSH  etc web services no longer function since a connection to the application server can not be made.
I think this is due to the HTTP Connector component being tied to TLS1.0 with no possibility to configure it to utilize any other https protocol.
I assume this will become more prevalent as more and more services upgrade to TLS 1.2. It seems an oversight that the HTTP Connector component can't support it.

Has anyone else encountered a similar issue - what workarounds, if any, helped to address the problem?
@Biovia - please confirm if the HTTP Connector component cannot indeed support web service requests to a server running TLS 1.2. If it can then clearly we're doing something wrong on our end.
Many thanks,

Running 2017 R2
Best Answer chosen by TMagnay
Simple solution - make sure you really are running 2017 R2 (minimum).

Unfortunately I was under the misconception that we were running 2017 R2 when we actually still on 2017 R1.
Upgraded to R2 and HTTP Connector totally works with TLS 1.2 compliant servers now.

Case solved! Many thanks to  BIOVIA support (Baskaran) for staying with me through all that.