NEP / JNEP Do Not Start After Deploying Cartridges
Last updated on MARCH 22, 2017
Applies to:Oracle Communications ASAP - Version 5.2.2 to 7.2.0 [Release 5.2 to 7.2]
Information in this document applies to any platform.
***Checked for relevance on 30-Jan-2014***
When two new custom cartridges are deployed, the Network Element Processor (NEP) and Java NEP (JNEP) servers are not starting in Production environment. These two cartridges support different versions of the same NE.
Same ASAP builds are working fine (i.e. NEP and JNEP start normally) in Development and pre-Production environments when these two cartridges are installed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms