I would like to know if we will be able to do security vulnerability, license and copyright scan using with sonatype nexus lifecycle for ruby gems?
I was not able to tun a trial version of IQ server due to licence requirements and see for myself. The free Application Health Check (AHC) seems to support only java based programs.
Please clarify.
IQ Server 1.35 introduced Lifecycle XC which has very basic support for RubyGems (and other formats that are not support by Sonatype yet), but that won't provide what you're looking for.
Recently announced IQ Server 1.46 enabled RubyGems support in Nexus Firewall. This might be good enough for what you're looking for.
However if you need RubyGems support in Nexus Lifecycle, then you have to wait for that.
Related
I am trying to implement code where I can send and receive the SOAP messages to IBM MQ. As of my knowledge jar file are required for my code to work, but could not find any place where either I can download the files or can do whole setup of WebSphere 6.0
Do anyone have any idea how can I get it ?
Please be aware that grabbing the jar files from an MQ Server or other installation is not supported by IBM and never has been. However, because it is one of the most commonly used methods to install the MQ client for Java or JMS and fairly common in Java developer culture, IBM has provided a Java-only install option. Please see the Redistributable Clients page in the Knowledge Center for details.
As the name suggests, this install provides an MQ Client package that can be redistributed with independently developed MQ applications. While that is helpful, the main reason IBM provides it is to provide a lightweight install package that...
Contains the correct and complete set of jar files as packaged by IBM.
Is intact and verifiable against a known specification and inventory.
Can reliably be expected to perform as per the documentation set for that version.
Contains all of IBM's diagnostic utilities both in the compiled binaries and in the Java classes.
Contains additional utilities such as GSKit for managing certificates.
Can be patched using IBM's standard Fix Pack install media so that integrity of the installed classes and libraries is preserved.
When using IBM's install media and procedure, the result is far more stable but int he event something goes wrong, the presence of the diagnostic utilities and conformance to a standard install procedure can dramatically reduce outage durations.
Also, there are occasional instances in which a customer with full support entitlements is told that their non-standard installation is not supported and they need to correct it before continuing the PMR. Though this doesn't happen often, in most cases the problem is resolved when the MQ client is installed according to spec. When that doesn't fix it, at least diagnostics can proceed at a faster pace.
The link above has all the details, including links to the client downloads, and is highly recommended reading. You can also go directly to Fix Central for the downloads. Fix Central offers all supported MQ client versions and the relocatable clients come in v8.0 and up. In the download list, look for the "All Java" package.
As Tim noted, mixing client and server versions is supported, provided both client and server are currently in service. Generally you want to develop against the latest version of MQ client because it has the most recent client-side features and will have the longest service life before a version upgrade is required.
Assuming you're on a Unix platform for your queue manager, the client will be found at:
/opt/mqm/java/lib
However, all MQ clients are compatible with all queue manager versions. I strongly recommend you use a client which is still supported, which means 7.1, 7.5, 8.0, or 9.0 at time of writing. These are freely downloadable from the SupportPac website.
The SupportPacs of interest are those starting 'MQC'. SupportPac MQC8 for example contains the MQ V8.0 client.
Thanks everyone. Just an update to the above answer. In my case I have asked the WebSphere administrator for providing me the lib folders which contains all the required MQ jar files.
I have asked him to provide following files from the C:\Program Files (x86)\IBM\WebSphere MQ\Java\lib\ folders:
* com.ibm.mq.jar
* connector.jar
* com.ibm.mq.jmqi.jar
* com.ibm.mq.headers.jar
* com.ibm.mq.commonservices.jar
We successfully setup the Meteor 0.7.1.2 in Centos. Is it Latest version supporting installation in windows 8 officially?. If yes please share the information.
we know its supporting unofficially with the following url
http://win.meteor.com
Thanks
Ramu
I agree about the cloud solutions. I've used the unofficial Windows version and had some problems, but I am loving cloud development with Meteor.
If you are interested in trying it out, I wrote up an entire tutorial on how to get set up with cloud development in Meteor and included a screencast.
http://simpleprogrammer.com/2014/10/13/getting-started-meteor-tutorial-cloud/
Windows support is not yet official and win.meteor.com outlines some workarounds, the better ones which include utilizing a virtual machine. There is a suggested native solution (launchmeteor.exe), although unofficial, with key difference (for some developers) being Meteorite not work on Windows yet.
According to the roadmap trello board https://trello.com/c/ZMvnfMfI/11-official-windows-support official windows support is targeted for 1.0 if time permits, but it seems very unlikely.
For interim portability, you may want to have a look at cloud solutions like nitrous.io at http://help.nitrous.io/meteor-app/ which runs the dev environment on the cloud but has a windows desktop app http://blog.nitrous.io/2014/02/25/nitrous-desktop-is-now-available-for-windows.html which at least lets you develop locally and sync to your nitrous.io cloud box.
I've seen this question but the answers are simply not good enough. I've searched the web and could find a clear listing of the main differences.
I am particularly surprised to see contradictions in the above link, that holds only 4 short answers.
So the question is, beyond support, what are (all) the differences between Alfresco Community and Enterprise editions (for the current versions of course)?
Are there functional or technical features that available in the Enterprise edition, that are not in the community edition?
I find it strange that it's so difficult to get a clear list. Looking at the forums to find this answer is not a serious option from a business perspective.
Until now, I found this link to be useful, but it's from 2009.
In particular, I find the platform support interesting, with the community edition supporting only lamp stuff:
Linux
MySQL
Tomcat
OpenLDAP
Firefox
And the enterprise edition supporting:
Windows
SQL Server
WebLogic, WebSphere
AD/Kerberos
IE and Safari
Apparently, these features are only available in the enterprise edition:
JMX monitoring
Runtime admininstration: What's that exactly? And what's in the community edition then?
Runtime indexing consistency check and update: What's in the community edition then?
High performance and availability: How is that implemented and what's in the community edition then?
Storage policies
Open source and proprietary technology stack support: which ones exaclty? Which ones are supported in the community edition?
If anyone could guide me towards serious documentation about these differences, that would be great.
I also went through the wiki but could not find an answer to my questions in there.
differences between Enterprise and Community vary in detail from version to version and are mainly visible for administrators. We see or maintain both flavors of Alfresco in midsize to very large environments and I would say it's more or less a question of taste and budget what the best decision / edition is for you. Excellent skills in infrastructure and java are highly advisable for both editions to run Alfresco in production.
The technical differences are not as dramatic as not being able to provide very similar functionality for the users - so if you're actually in a decision you should focus on a good technical partner, the support services and maybe the fact that you only get official patches in the Enterprise subscription, not on the Community. BTW Alfresco Enterprise is not Open Source but this is not a real point of interest for most end users. You can access the code as a subscription customer but it is not public available/accessible.
The main differences in features are already named more or less:
Administration
Enterprise has more views and setting in the admin web GUI. In Community you can access most configuration only from the command line. This may be a restriction but in real live Administrators prefer the command line and scripting automation.
Enterprise lets you change some Alfresco settings during runtime (most settings still require restart). Some can be change in the GUI and more in the jmx interface. Also you're able to stop and start subsystems like the CIFS protocol server. We use this feature to switch a system in read only mode. This point is meant with "runtime admininstration". Community requires restart of the service for most configuration changes. It is possible to work around this by advanced scripting like groovy or by implementing modules.
Indexing
Runtime indexing consistency check and update is not a self healing functionality as expected. You will have to learn (at least for now) that you have to recreate the Alfresco index from time to time even in Enterprise environments and that it is better to focus on good strategies how to speed recreation or how to setup standby indexes instead of hunting failed indexing transactions using the check and update methods. For major document model changes you need to recreate the index anyway.
High performance and availability
This is mainly the cluster and replication functionality which is no longer available in Community. It's similar to MS Clusters: It's a lot, lot work for very view more availability since some concepts are missing. The price is high in terms of complexity and can end up in loss of robustness. Even with enterprise support it's a hard job to keep a alfresco cluster running - so you need very good arguments why to go this way. But of course: its possible and available!
High performance: There shouldn't be any difference and if - I'm very curious about the explanation.
Technology stack
The main difference is the database support. In the Community you only can choose between MySQL and Postgres (No Oracle or MS SQL for Community). All other technologies are independent from Enterprise or Community (AD, Kerberos, OS, Browser, ...)
Java Container: I believe over 95% of all Alfresco installations run in tomcat. That's the configuration which is documented, tested and scales. Using WebLogic or WebSphere gives you no added value except new challenges - quite the contrary: You have to solve most issues for yourself and can't benefit from others experience.
Storage policies: I'm not pretty sure and should check in 4.2.x if the Content Store Selector / Storage policies is no longer available in the Community, but it was there in the 3.x versions.
[Edit]: storage policies have been removed in Community 4.2.x:
NoSuchBeanDefinitionException: No bean named 'storeSelectorContentStoreBase' is defined
If there is a really need for this functionality someone may re-enable that feature by coding a module for Community.
Regards
This page explains the difference between the editions:
https://wiki.alfresco.com/wiki/Enterprise_Edition
This page is the canonical, comprehensive list of the differences.
If you are considering an Enterprise Subscription and you have a question that isn't answered by what you can find on that page, you should talk to your account rep.
Well, regarding JMX monitoring:
Runtime administration: Alfresco enterprise allows to perform certain actions on Alfresco subsystems without restarting the server. This allows you to be very fast during debugging/developing and also making changes in production environment. Also you can access the JMX interface that supports JMX Remoting.
There is no consistency check or update, until you restart the server (during the startup you have to validate/check/rebuild your indexes). There is an option in alfresco.global.properties (or the original repository.properties config file) for that. If you have some inconsistencies in the Alfresco Community index, you're gonna have a bad time xD.
Alfresco Enterprise has specific license for clustering your architecture, the Community edition doesn't support those systems. Replicate and cluster Alfresco is one of the main improvements in performance/scalability/availability you could achieve.
The storage policies allow you to use Content Store selectors in Alfresco Enterprise. You can manage a primary and a secondary file store, and map/connect these stores in your architecture. The Community Edition allows you only to use one content store at a time.
These include everything inside Alfresco (Spring Framework, Apache-Lucene/Solr, Tomcat, and so on), because with the Enterprise license you have also the full support with everything inside the Alfresco package. The difference is that the Community is based on daily builds, supported by community, and therefor not guaranteed. The Enterprise support helps you resolve many problems that you might encounter during developing and in production environment, not only Alfresco related, but also on some configurations on supported platforms (Windows/Linux), your web application servers, and so on.
Hope it helps.
I tried the usual:
CRX from Day.com: not (yet) stable
KnowledgeTree Community: couldn't get it to work (unless perhaps you buy the commercial version?)
Nuxeo: very, very expensive, but looks good (is there a community version available?)
yet a few more
I also installed Alfresco, which seems to be the best out there in terms of functions it offers; I'm quite impressed by it, to be honest. However, it's very slow, sometimes taking a few minutes to check-in a document. It also takes quite a lot of memory (maybe due to Java?). It also has some issues dealing with Illustrator documents.
Is there a CMIS server available that can connect to Adobe Drive (CMIS) and not running on Java?
I just need the Check-in/out functions through Adobe Drive 2.1 or 3.0 CMIS.
UPDATE [20/02/2012]
After playing with the above-mentioned software for a while, I can (personally) affirm that Alfresco is the best among all (free) available software. I'm running the community version 4.0.d. It seems pretty stable and the installation + connexion to Adobe Drive 3.0.1 via the CMIS connector is seamless; (FYI in Drive: cmis://127.0.0.1:8080/alfresco/service/cmis).
UPDATE [25/06/2014]
#NicolasRaoul is right. CMIS not running on Java, as specified in the title => Nuxeo. Hence #JulienCarsique's answer accepted/upvoted.
About Nuxeo, it is free for use. There's no "community" or "enterprise" versions but a unique Open-Source, free and enterprise-ready version.
To answer your question, there is a CMIS implementation that is not based on Java. It is Microsoft Sharepoint, which also has a CMIS connector. I don't know anything about it's completeness or performance.
Something tells me though that is not the platform you are looking for and it will definitely not run on your Mac Mini.
After playing with the above-mentioned software for a while, I can (personally) affirm that Alfresco is the best among all (free) available software. I'm running the community version 4.0.d. It seems pretty stable and the installation + connexion to Adobe Drive 3.0.1 via the CMIS connector is seamless; (FYI in Drive: cmis://127.0.0.1:8080/alfresco/service/cmis).
I've heard somewhere that LCDS is no longer baked in into CF9, and LCDS Express will be phased out, is that true?
If I were to start a new CF8.01 + LCDS Express 2.6 project, what are the risks? Should I abandon that plan and go for BlazeDS instead?
Thanks.
For the record:
ColdFusion 8 shipped (as part of the installer) LCDS 2.6 Express. LCDS Express (free) is no longer available so it is not shipped with ColdFusion 9. However, ColdFusion 9 still supports the same level of integration w/ LCDS as in ColdFusion. The only difference is the installation process. Of course, without a free edition of LCDS, you would be required to purchase a production license.
ColdFusion 9.01 (codenamed Sully) will have full support for LCDS 3.1. It's scheduled for release in mid-2010.
-Adam
Henry just informed me of this thread and showed me the articles on FB4's "Data Management". Forgive my ignorance at this time as I need to carefully read them not just skim them, but I'll chime in briefly.
It sounds to me that FB4's "client-side data management without having to use a server at all" is semantically clear as mud. How does an individual client manage data as "LCDS Data Management" feature does? (Who's on first?). Sounds like they are being implied to be the same. What about NIO, RTMP, Conflict Resolution, server-to-client Pagination, Lazy Loading, etc?
Given the near complete overlap in jargon, and analogous implementations, I think Adobe should be VERY clear regarding the difference. I suppose its in Adobe's best interest to differentiate LCDS Data Management proper (the money feature) from FB4 Data Management (the freebie) if it wants good selling points for LCDS customers.
AFAIK, LCDS 2.6.1 full installer runs as unlimited version for 120 days, and then reverts to the Express Edition 1-CPU (a.k.a. Single CPU Edition) thereafter. If you are already running LCDS 2.6.1 as Single CPU Edition as a standalone server you can connect ColdFusion 8.0/1 and ColdFusion 9.0 to it via RMI by checking the CF Admin boxes under Enable Remote LCDS Access. However, if you have the LCDS 2.6.1 Components for ColdFusion and a full LCDS 2.6.1 server bits lying around, then you can use it to configure both ColdFusion 8.x and ColdFusion 9.0 for an embedded version of LCDS (where they both run in the same JVM and do not need RMI to talk to eachother). I have LCDS 2.6.1 working in embedded mode with both CF8.01 and CF9.0.
Additionally, regarding "LCDS Express (free) is no longer available", it may be true that you can not download it off Adobe.com anymore, but if you already have it then Adobe won't retroactively change your EULA.
How are you specifically planning to use the Data Management? Flash Builder 4 includes the ability to do client-side data management without having to use a server at all. CF also gives you the ability to do online/offline synchronization and datamanagement with CF and AIR.
LCDS 3.0 has some interesting functionality that goes above and beyond data management but if you're looking at basic data management you might want to give one of the two options above a try.
=Ryan
ryan#adobe.com
To use LiveCycle Data Services ES
2.6.1 with ColdFusion 9, you need to manually install it after completing
your ColdFusion 9 installation.
http://help.adobe.com/en_US/ColdFusion/9.0/Installing/WSB53CBD63-A21C-4f31-8F3E-700AE45A026E.html
Nice, LCDS still supported.