Have you looked at Spring configuration ? That way you can/create a map in config and store object definitions per key. e.g.
<map>
<entry key="India" value="Delhi">
</map>
You're talking about business rules but at the moment you're simply storing a key/value pair. If those rules become more complex then a simple key/value pair won't suffice. So perhaps you need something like:
Map<String, Country>
in your code, and Country is an object with (for now) a capital city, but in the future it would contain (say) locations, or an international phone number prefix, or a tax rule etc. In Spring it would resemble:
<map>
<entry key="India" ref="india"/>
</map>
<!-- create a subclass of Country -->
<bean id="india" class="com.example.India">
I realise this is considerably more complex than the other suggestions here. However since you're talking about rules, I suspect you'll be looking to configure/define some sort of behaviour. You can do this using properties (or similar) but likely you'll end up with different properties sets for the different behavioural aspects of your rules. That rapidly becomes a real maintenance nightmare.