Custom portal extension deployment with CLI on JPP 6

Solution Verified - Updated -

Issue

  • Operations reports that deploying a portal artefact using CLI (“deploy –server-group=xxxxxx /tmp/deployable.ear”) on JPP puts the file in standalone/deployments instead of gatein/extensions. How can we change this behavior?

Environment

  • Red Hat JBoss Portal (JPP)
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.